mirror of
https://github.com/nushell/nushell.git
synced 2024-11-24 17:34:00 +01:00
a88f46c6c9
# Description With Windows Terminal Canary 1.23.240826001-llm, this enables nushell to query the terminal and receive a response. ![image](https://github.com/user-attachments/assets/c4c43328-c431-47e4-b377-8b3a2bc12b74) The red component here is ```nushell ❯ ("0c0c" | into int -r 16) / 256 | math round | fmt | get lowerhex 0xc ``` This example queries the background and the response is a r/g/b color. The response really should be ``` ␛]11;1;rgb:0c0c/0c0c/0c0c ``` I'm not sure why nushell's input is eating the first part. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use toolkit.nu; toolkit test stdlib"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> |
||
---|---|---|
.. | ||
src | ||
.gitignore | ||
Cargo.toml | ||
LICENSE | ||
README.md |
Collection of small utilities that are shared across Nushell crates.
This crate should compile early in the crate graph and thus not depend on major dependencies or core-nushell crates itself.
Internal Nushell crate
This crate implements components of Nushell and is not designed to support plugin authors or other users directly.