forked from extern/nushell
1e39a1a7a3
# Description This PR fixes a bug that prevented you from having multiple modifiers on your keybindings. TODO: - The docs need to be fixed too https://www.nushell.sh/book/line_editor.html#keybindings. (https://github.com/nushell/nushell.github.io/pull/840) - I think reedline needs to be changed to show this too since it provides the list of available modifiers. (https://github.com/nushell/reedline/pull/559) Now you can do something like this where `shift` and `alt` are combined with an underscore. ``` { name: fuzzy_history_fzf modifier: shift_alt keycode: char_r mode: [emacs , vi_normal, vi_insert] event: { blah } ``` Here's the list of available combinations ```rust "control" => KeyModifiers::CONTROL, "shift" => KeyModifiers::SHIFT, "alt" => KeyModifiers::ALT, "none" => KeyModifiers::NONE, "shift_alt" | "alt_shift" => KeyModifiers::SHIFT | KeyModifiers::ALT, "control_shift" | "shift_control" => KeyModifiers::CONTROL | KeyModifiers::SHIFT, "control_alt" | "alt_control" => KeyModifiers::CONTROL | KeyModifiers::ALT, "control_alt_shift" | "control_shift_alt" => { KeyModifiers::CONTROL | KeyModifiers::ALT | KeyModifiers::SHIFT } ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass > **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. |
||
|---|---|---|
| .. | ||
| nu_plugin_custom_values | ||
| nu_plugin_example | ||
| nu_plugin_formats | ||
| nu_plugin_gstat | ||
| nu_plugin_inc | ||
| nu_plugin_python | ||
| nu_plugin_query | ||
| nu-cli | ||
| nu-cmd-lang | ||
| nu-color-config | ||
| nu-command | ||
| nu-engine | ||
| nu-explore | ||
| nu-glob | ||
| nu-json | ||
| nu-parser | ||
| nu-path | ||
| nu-plugin | ||
| nu-pretty-hex | ||
| nu-protocol | ||
| nu-system | ||
| nu-table | ||
| nu-term-grid | ||
| nu-test-support | ||
| nu-utils | ||
| README.md | ||
Nushell core libraries and plugins
These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.
Foundational libraries are split into two kinds of crates:
- Core crates - those crates that work together to build the Nushell language engine
- Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.
Plugins are likewise also split into two types:
- Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
- Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.