holm/nushell
1
1
Fork 0
forked from extern/nushell
Code Issues Pull Requests Packages Projects Releases Wiki Activity
fe60fb8679
nushell/crates/nu-cli/Cargo.toml

45 lines
1.3 KiB
TOML
Raw Normal View History

Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
[package]
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
authors = ["The Nushell Project Developers"]
Update incorrect crate descriptions (#5159)
2022-04-11 20:17:06 +02:00
description = "CLI-related functionality for Nushell"
Add repository info to all workspace crates (#6320) This helps people who find these crates on crates.io
2022-08-14 14:21:20 +02:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-cli"
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
edition = "2021"
license = "MIT"
Bump to 0.16.1 (#2116)
2020-07-05 22:12:44 +02:00
name = "nu-cli"
Bump to `0.79.1` dev version (#8998) # Description For development or hotfixes
2023-04-26 01:05:23 +02:00
version = "0.79.1"
refactor to subcrates
2021-08-10 20:51:08 +02:00
Disable auto-benchmark harness for crates (#8057) # Description This disables automatic detection of `#[bench]` and other benchmarks within the crates. Our benchmarks should all live in `benches` This fixes a problem with criterion flags and should also reduce the build requirements for `cargo bench` a bit Taken from https://github.com/nushell/nushell/pull/7952 See: https://bheisler.github.io/criterion.rs/book/faq.html#cargo-bench-gives-unrecognized-option-errors-for-valid-command-line-options # User-Facing Changes None
2023-02-12 23:22:00 +01:00
[lib]
bench = false
nu-cli: added tests for file completions (#5232) * nu-cli: added tests for file completions * test adding extra sort * Feature/refactor completion options (#5228) * Copy completion filter to custom completions * Remove filter function from completer This function was a no-op for FileCompletion and CommandCompletion. Flag- and VariableCompletion just filters with `starts_with` which happens in both completers anyway and should therefore also be a no-op. The remaining use case in CustomCompletion was moved into the CustomCompletion source file. Filtering should probably happen immediately while fetching completions to avoid unnecessary memory allocations. * Add get_sort_by() to Completer trait * Remove CompletionOptions from Completer::fetch() * Fix clippy lints * Apply Completer changes to DotNuCompletion * add os to $nu based on rust's understanding (#5243) * add os to $nu based on rust's understanding * add a few more constants Co-authored-by: Richard <Tropid@users.noreply.github.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-04-20 06:54:00 +02:00
[dev-dependencies]
Bump to `0.79.1` dev version (#8998) # Description For development or hotfixes
2023-04-26 01:05:23 +02:00
nu-test-support = { path = "../nu-test-support", version = "0.79.1" }
Bump rstest from 0.16.0 to 0.17.0 (#8534)
2023-03-20 18:27:29 +01:00
rstest = { version = "0.17.0", default-features = false }
nu-cli: added tests for file completions (#5232) * nu-cli: added tests for file completions * test adding extra sort * Feature/refactor completion options (#5228) * Copy completion filter to custom completions * Remove filter function from completer This function was a no-op for FileCompletion and CommandCompletion. Flag- and VariableCompletion just filters with `starts_with` which happens in both completers anyway and should therefore also be a no-op. The remaining use case in CustomCompletion was moved into the CustomCompletion source file. Filtering should probably happen immediately while fetching completions to avoid unnecessary memory allocations. * Add get_sort_by() to Completer trait * Remove CompletionOptions from Completer::fetch() * Fix clippy lints * Apply Completer changes to DotNuCompletion * add os to $nu based on rust's understanding (#5243) * add os to $nu based on rust's understanding * add a few more constants Co-authored-by: Richard <Tropid@users.noreply.github.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-04-20 06:54:00 +02:00
refactor to subcrates
2021-08-10 20:51:08 +02:00
[dependencies]
Bump to `0.79.1` dev version (#8998) # Description For development or hotfixes
2023-04-26 01:05:23 +02:00
nu-command = { path = "../nu-command", version = "0.79.1" }
nu-engine = { path = "../nu-engine", version = "0.79.1" }
nu-path = { path = "../nu-path", version = "0.79.1" }
nu-parser = { path = "../nu-parser", version = "0.79.1" }
nu-protocol = { path = "../nu-protocol", version = "0.79.1" }
nu-utils = { path = "../nu-utils", version = "0.79.1" }
nu-color-config = { path = "../nu-color-config", version = "0.79.1" }
Bump version for `0.76.0` release (#8121) Before landing: - [x] `reedline 0.16.0` is out and pinned. - [x] all fixes and features necessary are landed. In the meantime: - [ ] feed the release notes with relevant features and breaking changes
2023-02-21 21:46:29 +01:00
Bump version to `0.77.0` (#8410)
2023-03-14 19:46:42 +01:00
nu-ansi-term = "0.47.0"
Pin `reedline` to `0.19.0` release (#8996) # Description See release notes: https://github.com/nushell/reedline/releases/tag/v0.19.0
2023-04-25 20:58:33 +02:00
reedline = { version = "0.19.0", features = ["bashisms", "sqlite"]}
Help menu (#4992) * nu-completer with suggestions * help menu with scrolling * updates description rows based on space * configuration for help menu * update nu-ansi-term * corrected test for update cells * changed keybinding
2022-03-27 15:01:04 +02:00
Terminate REPL if not connected to tty input (#6480) * Terminate REPL if not connected to tty input If the standard input stream is not a TTY abort the REPL execution. Solves a problem as the current REPL tries to be IO fault tolerant and would indefinetely fail when crossterm tries to handle the STDIN. Fixes nushell/nushell#6452 * Improve the error message
2022-09-05 13:33:54 +02:00
atty = "0.2.14"
chore: chrono_update (#7132) chrono version update # Description upgrade chrono to 0.4.23 # Major Changes If you're considering making any major change to nushell, before starting work on it, seek feedback from regular contributors and get approval for the idea from the core team either on [Discord](https://discordapp.com/invite/NtAbbGn) or [GitHub issue](https://github.com/nushell/nushell/issues/new/choose). Making sure we're all on board with the change saves everybody's time. Thanks! # Tests + Formatting Make sure you've done the following, if applicable: - Add tests that cover your changes (either in the command examples, the crate/tests folder, or in the /tests folder) - Try to think about corner cases and various ways how your changes could break. Cover those in the tests 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 --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace --features=extra` to check that all tests pass # After Submitting * Help us keep the docs up to date: If your PR affects the user experience of Nushell (adding/removing a command, changing an input/output type, etc.), make sure the changes are reflected in the documentation (https://github.com/nushell/nushell.github.io) after the PR is merged. Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-11-26 19:19:02 +01:00
chrono = { default-features = false, features = ["std"], version = "0.4.23" }
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
crossterm = "0.26"
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
fancy-regex = "0.11.0"
replace the regex crate with the fancy-regex crate (#6227)
2022-08-04 21:51:02 +02:00
fuzzy-matcher = "0.3.7"
Handle Windows drive paths in auto-cd (#6051) * Handle Windows drive paths in auto-cd * Limit `use regex` to Windows * Use lazy_static for Windows drive path regex * try fixing Clippy on *nix
2022-07-16 04:01:38 +02:00
is_executable = "1.0.1"
Bump once_cell from 1.16.0 to 1.17.0 (#7732)
2023-01-12 00:00:44 +01:00
once_cell = "1.17.0"
Handle Windows drive paths in auto-cd (#6051) * Handle Windows drive paths in auto-cd * Limit `use regex` to Windows * Use lazy_static for Windows drive path regex * try fixing Clippy on *nix
2022-07-16 04:01:38 +02:00
log = "0.4"
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
miette = { version = "5.7.0", features = ["fancy-no-backtrace"] }
shell_integration: Report current working directory as OSC 7 (#6481) This is a de-facto standard supported by many terminals, originally added to macOS Terminal.app, now also supported by VTE (GNOME), Konsole (KDE), WezTerm, and more.
2022-09-13 14:36:53 +02:00
percent-encoding = "2"
Fix CPU usage info in `sys` (#8321) Closes #8264. This PR does a few things to fix the `usage` column in `sys.cpu`: 1. Sleep a while (~400ms) between calls to `sys.refresh_cpu()`, [as required by `sysinfo`](https://docs.rs/sysinfo/latest/sysinfo/trait.SystemExt.html#method.refresh_cpu) 2. Change `sys` to return a `LazyRecord` (so you can do things like `sys | get host` instantly without waiting for CPU info) 3. Update our `sysinfo` dependency to [fix CPU usage calculations on Linux](https://github.com/GuillaumeGomez/sysinfo/pull/946) CPU usage is no longer always reported as zero: ![image](https://user-images.githubusercontent.com/26268125/222929775-5e9cbe18-95d9-4ecb-baf8-1e843f5c7086.png)
2023-03-04 23:48:34 +01:00
sysinfo = "0.28.2"
replace the regex crate with the fancy-regex crate (#6227)
2022-08-04 21:51:02 +02:00
thiserror = "1.0.31"
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
unicode-segmentation = "1.10.0"
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
[features]
plugin = []
Reference in New Issue Copy Permalink