forked from extern/nushell
fedd879b2e
should close https://github.com/nushell/nushell/issues/7202 # Description i have been annoyed enough by this missing feature, so let's add that to Nushell without requiring any user configuration 😏 # User-Facing Changes this PR should allow tab completion cycling everytime, without requiring the user to use the default config files or add the following keybindings to their config ```nushell { name: completion_menu modifier: none keycode: tab mode: [emacs vi_normal vi_insert] event: { until: [ { send: menu name: completion_menu } { send: menunext } { edit: complete } ] } } ``` ### 🧪 try it out from the root of the repo, one can try `<tab>` in each of the following cases: - `cargo run -- -n` to load Nushell without any config - `cargo run -- --config crates/nu-utils/src/sample_config/default_config.nu --env-config crates/nu-utils/src/sample_config/default_env.nu` to load the default configuration - `cargo run` to load the user configuration ## before - `<tab>`, `ls <tab>` and `str <tab>` only work with the second `cargo run`, i.e. when loading the default config files ## after - `<tab>` should cycle through the available commands - `ls <tab>` should cycle through the available files and directories - `str <tab>` should cycle the subcommands of `str` in all three cases # Tests + Formatting # After submitting |
||
---|---|---|
.. | ||
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.