extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2025-02-19 03:51:11 +01:00
Code Issues Packages Projects Releases Wiki Activity
b48f50f018
nushell/crates/nu-cli/src/lib.rs

38 lines
1016 B
Rust
Raw Normal View History

Add top-level crate documentation/READMEs (#12907) # Description Add `README.md` files to each crate in our workspace (-plugins) and also include it in the `lib.rs` documentation for <docs.rs> (if there is no existing `lib.rs` crate documentation) In all new README I added the defensive comment that the crates are not considered stable for public consumption. If necessary we can adjust this if we deem a crate useful for plugin authors.
2024-07-14 10:10:41 +02:00
#![doc = include_str!("../README.md")]
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
mod commands;
Finish up completions
2021-09-10 00:09:40 +02:00
mod completions;
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
mod config_files;
Move CLI related commands to `nu-cli` (#8832) # Description Part of the larger cratification effort. Moves all `reedline` or shell line editor specific commands to `nu-cli`. ## From `nu-cmd-lang`: - `commandline` - This shouldn't have moved there. Doesn't directly depend on reedline but assumes parts in the engine state that are specific to the use of reedline or a REPL ## From `nu-command`: - `keybindings` and subcommands - `keybindings default` - `keybindings list` - `keybindings listen` - very `reedline` specific - `history` - needs `reedline` - `history session` ## internal use Instead of having a separate `create_default_context()` that calls `nu-command`'s `create_default_context()`, I added a `add_cli_context()` that updates an `EngineState` # User-Facing Changes None ## Build time comparison `cargo build --timings` from a `cargo clean --profile dev` ### total main: 64 secs this: 59 secs ### `nu-command` build time branch | total| codegen | fraction ---|---|---|--- main | 14.0s | 6.2s | (44%) this | 12.5s | 5.5s | (44%) `nu-cli` depends on `nu-command` at the moment. Thus it is built during the code-gen phase of `nu-command` (on 16 virtual cores) # Tests + Formatting I removed the `test_example()` facilities for now as we had not run any of the commands in an `Example` test and importing the right context for those tests seemed more of a hassle than the duplicated `test_examples()` implementations in `nu-cmd-lang` and `nu-command`
2023-04-10 00:56:47 +02:00
mod eval_cmds;
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
mod eval_file;
Generic menus (#5085) * updated to reedline generic menus * help menu with examples * generic menus in the engine * description menu template * list of menus in config * default value for menu * menu from block * generic menus examples * change to reedline git path * cargo fmt * menu name typo * remove commas from default file * added error message
2022-04-04 16:54:48 +02:00
mod menus;
Highlight help tutor (#838) * WIP * Syntax highlight help, add tutor
2022-01-24 16:05:19 +01:00
mod nu_highlight;
Add an explicit 'print' command (#4535)
2022-02-18 19:43:34 +01:00
mod print;
prompt with env variable
2021-10-02 15:10:28 +02:00
mod prompt;
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
mod prompt_update;
mod reedline_config;
mod repl;
refactor to subcrates
2021-08-10 20:51:08 +02:00
mod syntax_highlight;
Add an explicit 'print' command (#4535)
2022-02-18 19:43:34 +01:00
mod util;
multiline validation
2021-09-22 07:29:53 +02:00
mod validation;
refactor to subcrates
2021-08-10 20:51:08 +02:00
Move CLI related commands to `nu-cli` (#8832) # Description Part of the larger cratification effort. Moves all `reedline` or shell line editor specific commands to `nu-cli`. ## From `nu-cmd-lang`: - `commandline` - This shouldn't have moved there. Doesn't directly depend on reedline but assumes parts in the engine state that are specific to the use of reedline or a REPL ## From `nu-command`: - `keybindings` and subcommands - `keybindings default` - `keybindings list` - `keybindings listen` - very `reedline` specific - `history` - needs `reedline` - `history session` ## internal use Instead of having a separate `create_default_context()` that calls `nu-command`'s `create_default_context()`, I added a `add_cli_context()` that updates an `EngineState` # User-Facing Changes None ## Build time comparison `cargo build --timings` from a `cargo clean --profile dev` ### total main: 64 secs this: 59 secs ### `nu-command` build time branch | total| codegen | fraction ---|---|---|--- main | 14.0s | 6.2s | (44%) this | 12.5s | 5.5s | (44%) `nu-cli` depends on `nu-command` at the moment. Thus it is built during the code-gen phase of `nu-command` (on 16 virtual cores) # Tests + Formatting I removed the `test_example()` facilities for now as we had not run any of the commands in an `Example` test and importing the right context for those tests seemed more of a hassle than the duplicated `test_examples()` implementations in `nu-cmd-lang` and `nu-command`
2023-04-10 00:56:47 +02:00
pub use commands::add_cli_context;
Send LSP Completion Item Kind (#11443) # Description This commit fills in the completion item kind into the `textDocument/completion` response so that LSP client can present more information to the user. It is an improvement in the context of #10794 # User-Facing Changes Improved information display in editor's intelli-sense menu ![output](https://github.com/nushell/nushell/assets/16558417/991dc0a9-45d1-4718-8f22-29002d687b93)
2024-03-25 02:14:12 +01:00
pub use completions::{FileCompletion, NuCompleter, SemanticSuggestion, SuggestionKind};
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
pub use config_files::eval_config_contents;
Change the error style during tests to `plain` (#13061) # Description This fixes issues with trying to run the tests with a terminal that is small enough to cause errors to wrap around, or in cases where the test environment might produce strings that are reasonably expected to wrap around anyway. "Fancy" errors are too fancy for tests to work predictably :wink: cc @abusch # User-Facing Changes - Added `--error-style` option for use with `--commands` (like `--table-mode`) # Tests + Formatting Surprisingly, all of the tests pass, including in small windows! I only had to make one change to a test for `error make` which was looking for the box drawing characters miette uses to determine whether the span label was showing up - but the plain error style output is even better and easier to match on, so this test is actually more specific now.
2024-06-19 06:37:24 +02:00
pub use eval_cmds::{evaluate_commands, EvaluateCommandsOpts};
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
pub use eval_file::evaluate_file;
Bump Reedline for the Menu Refactor (#11658) * [Refactor Menu System with Composition of Menu Functions](https://github.com/nushell/reedline/issues/706) * Move Description Menu over to Reedline to consolidate location of the Menus which will simplify further changes and maintenance to the Menu system going forward * Removes lots of code duplication in the Menu system on the Reedline side which should ease a developers ability to develop new cool menus for Reedline moving forward
2024-01-28 17:26:03 +01:00
pub use menus::NuHelpCompleter;
Highlight help tutor (#838) * WIP * Syntax highlight help, add tutor
2022-01-24 16:05:19 +01:00
pub use nu_highlight::NuHighlight;
Add an explicit 'print' command (#4535)
2022-02-18 19:43:34 +01:00
pub use print::Print;
prompt with env variable
2021-10-02 15:10:28 +02:00
pub use prompt::NushellPrompt;
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
pub use repl::evaluate_repl;
refactor to subcrates
2021-08-10 20:51:08 +02:00
pub use syntax_highlight::NuHighlighter;
feat: add a `command_not_found` hook (#8314) # Description Add a `command_not_found` function to `$env.config.hooks`. If this function outputs a string, then it's included in the `help`. An example hook on *Arch Linux*, to find packages that contain the binary, looks like: ```nushell let-env config = { # ... hooks: { command_not_found: { |cmd_name| ( try { let pkgs = (pkgfile --binaries --verbose $cmd_name) ( $"(ansi $env.config.color_config.shape_external)($cmd_name)(ansi reset) " + $"may be found in the following packages:\n($pkgs)" ) } catch { null } ) } # ... ``` # User-Facing Changes - Add a `command_not_found` function to `$env.config.hooks`. # 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 # 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.
2023-03-20 05:05:22 +01:00
pub use util::{eval_source, gather_parent_env_vars};
multiline validation
2021-09-22 07:29:53 +02:00
pub use validation::NuValidator;
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
#[cfg(feature = "plugin")]
pub use config_files::add_plugin_file;
#[cfg(feature = "plugin")]
Overhaul the plugin cache file with a new msgpack+brotli format (#12579) # Description - Plugin signatures are now saved to `plugin.msgpackz`, which is brotli-compressed MessagePack. - The file is updated incrementally, rather than writing all plugin commands in the engine every time. - The file always contains the result of the `Signature` call to the plugin, even if commands were removed. - Invalid data for a particular plugin just causes an error to be reported, but the rest of the plugins can still be parsed # User-Facing Changes - The plugin file has a different filename, and it's not a nushell script. - The default `plugin.nu` file will be automatically migrated the first time, but not other plugin config files. - We don't currently provide any utilities that could help edit this file, beyond `plugin add` and `plugin rm` - `from msgpackz`, `to msgpackz` could also help - New commands: `plugin add`, `plugin rm` # Tests + Formatting Tests added for the format and for the invalid handling. - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # After Submitting - [ ] Check for documentation changes - [ ] Definitely needs release notes
2024-04-21 14:36:26 +02:00
pub use config_files::migrate_old_plugin_file;
#[cfg(feature = "plugin")]
Move repl loop and command/script execution to nu_cli (#4846) * Refactor usage of is_perf_true to be a parameter passed around * Move repl loop and command/script execution to nu_cli * Move config setup out of nu_cli * Update config_files.rs * Update main.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-16 19:17:06 +01:00
pub use config_files::read_plugin_file;
Reference in New Issue Copy Permalink