forked from extern/nushell
8501024546
Supercedes https://github.com/nushell/nushell/pull/10196 # Description After reading https://github.com/nushell/nushell/pull/10196#issuecomment-1703986359 I added a signpost from `keybindings listen` to `input listen` When I initially tried `input listen` it always immediately returned with: ``` ╭───────┬────────╮ │ type │ focus │ │ event │ gained │ ╰───────┴────────╯ ``` I added an example to `input listen --help` to suggest only listening to key events Initially I also included a `result` but it prints as: ``` ╭───────────┬───────────────╮ │ type │ key │ │ key_type │ char │ │ code │ c │ │ modifiers │ [list 1 item] │ ╰───────────┴───────────────╯ ``` rather than: ``` ╭───────────┬───────────────────────────────╮ │ type │ key │ │ key_type │ char │ │ code │ c │ │ │ ╭───┬───────────────────────╮ │ │ modifiers │ │ 0 │ keymodifiers(control) │ │ │ │ ╰───┴───────────────────────╯ │ ╰───────────┴───────────────────────────────╯ ``` so I removed it. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> * Example describing how to use `input list --types [key]` to listen for keybindings. * Signpost pointing at `use std input; input list --types [key]` from `keybindings list`. ## After merging It is probably worth: a) signposting to the keybindings section of the book from both of these subcommands (like I did in https://github.com/nushell/nushell/pull/10193), b) giving an example in the book of how to take the output from `input listen --types [key]` and format it for including in `config nu` c) there are not currently any examples in crates/nu-utils/src/sample_config/default_config.nu for keybindings with multiple modifiers. Should I add alt+backspace-in-macos-vscode as an example (gets translated to `{ modifier: control_alt keycode: char_h }` for historical reasons)? --------- Co-authored-by: Antoine Stevan <44101798+amtoine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| 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-base | ||
| nu-cmd-dataframe | ||
| nu-cmd-extra | ||
| 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-std | ||
| 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.