Mirrors/nushell
2
0
Fork 0
mirror of https://github.com/nushell/nushell synced 2024-12-29 14:33:13 +00:00
Code Issues Projects Releases Packages Wiki Activity
nushell/Cargo.toml

179 lines
5.9 KiB
TOML
Raw Normal View History

objectshell initial commit
2019-05-10 16:59:12 +00:00
[package]
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 18:30:27 +00:00
authors = ["The Nushell Project Developers"]
REFACTOR: clean the root of the repo (#9231) # Description i've almost always wanted to clean up the root of the repo, so here is my take at it, with some important advice given by @fdncred :relieved: - `README.release.txt` is now gone and directly inline in the `release-pkg` script used in the `release` *workflow* - `build.rs` has been moved to `scripts/` and its path has been changed in [`Cargo.toml`](https://github.com/amtoine/nushell/blob/refactor/clean-root/Cargo.toml#L3) according to the [*Build Scripts* section](https://doc.rust-lang.org/cargo/reference/build-scripts.html#build-scripts) of *The Cargo Book* - i've merged `images/` into `assets/` and fix the only mention to the GIF in the README - i've moved the `docs/README.md` inside the main `README.md` as a new [*Configuration* section](https://github.com/amtoine/nushell/tree/refactor/clean-root#configuration) - the very deprecated `pkg_mgrs/` has been removed - all the `.nu`, `.sh`, `.ps1` and `.cmd` scripts have been moved to `scripts/` ### things i've left as-is - all the other `.md` documents - the configuration files - all the Rust and core stuff - `docker/` - `toolkit.nu` - the `wix/` diretory which appears to be important for `winget` # User-Facing Changes scripts that used to rely on the paths to some of the scripts should now call the scripts inside `scripts/` => i think this for the greater good, it was not pretty nor scalable to have a bunch of scripts in the root of our main `nushell` :scream: *i even think we might want to move these scripts outside the main `nushell` repo* maybe to `nu_scripts` or some other tool :+1: # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-05-20 12:57:51 +00:00
build = "scripts/build.rs"
Bump to 0.16.1 (#2116)
2020-07-05 20:12:44 +00:00
default-run = "nu"
Add experimental new parser (#1554) Move to an experimental new parser
2020-04-06 07:16:14 +00:00
description = "A new type of shell"
Bump to 0.16.1 (#2116)
2020-07-05 20:12:44 +00:00
documentation = "https://www.nushell.sh/book/"
Upgrade all remaining crates to Rust 2021 (#7681) 2 crates were still using Rust 2018, including the base `nu` crate. This PR upgrades them to Rust 2021. If you're aware of any reason why this is a bad idea, please speak now or forever hold your peace. ## Context I was moving benchmarks from `nu-plugin` to the base crate and couldn't figure out why they wouldn't compile. Turns out the benchmarks rely on some Rust 2021 features. Would be nice to have everything on 2021.
2023-01-05 12:24:42 +00:00
edition = "2021"
Bump to 0.16.1 (#2116)
2020-07-05 20:12:44 +00:00
exclude = ["images"]
homepage = "https://www.nushell.sh"
license = "MIT"
name = "nu"
Add readme and homepage/repo
2019-07-16 19:17:46 +00:00
repository = "https://github.com/nushell/nushell"
Update rust version (#5432)
2022-05-04 01:56:31 +00:00
rust-version = "1.60"
Bump version to `0.86.1` (#10755) To dev or to patch that is the question
2023-10-18 18:00:51 +00:00
version = "0.86.1"
first commit
2021-06-30 01:42:56 +00:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
Add binstall metadata (#7212) # Description To make `cargo binstall nu` works out of the box, `Cargo.toml` needs to be slightly modified, likely because the URL to the download does not exactly match. # User-Facing Changes None # Tests + Formatting Tested by cherry-picking this commit on top of the 0.71.0 tag, running `cargo package --allow-dirty --no-verify`, then: ``` ~ ❯ cargo binstall --manifest-path ~/src/github/nushell/nushell/Cargo.toml nu --force INFO resolve: Resolving package: 'nu' WARN resolve: The package will be downloaded from github.com INFO resolve: This will install the following binaries: INFO resolve: - nu (nu -> /home/michel/.cargo/bin/nu-v0.71.0) INFO resolve: And create (or update) the following symlinks: INFO resolve: - nu (/home/michel/.cargo/bin/nu -> nu-v0.71.0) Do you wish to continue? yes/[no] ? yes INFO install: Installing binaries... INFO Done in 8.538106765s ``` `--force` was needed because I've previously tried this to manually test the `pkg-url`: ``` cargo binstall \ --pkg-url="{ repo }/releases/download/{ version }/{ name }-{ version }-{ target }.{ archive-format }" \ --pkg-fmt="tgz" nu ``` Fixes #7201. Signed-off-by: Michel Alexandre Salim <michel@michel-slm.name> Signed-off-by: Michel Alexandre Salim <michel@michel-slm.name>
2022-11-23 16:46:06 +00:00
[package.metadata.binstall]
pkg-url = "{ repo }/releases/download/{ version }/{ name }-{ version }-{ target }.{ archive-format }"
pkg-fmt = "tgz"
[package.metadata.binstall.overrides.x86_64-pc-windows-msvc]
pkg-fmt = "zip"
Add a few operators. Needs parser work
2021-08-25 19:29:36 +00:00
[workspace]
plugin crate
2021-10-28 06:12:33 +00:00
members = [
"crates/nu-cli",
"crates/nu-engine",
"crates/nu-parser",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 06:20:53 +00:00
"crates/nu-system",
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 21:45:54 +00:00
"crates/nu-cmd-base",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 17:46:16 +00:00
"crates/nu-cmd-extra",
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ # 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 # 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-02-24 15:54:42 +00:00
"crates/nu-cmd-lang",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 17:56:08 +00:00
"crates/nu-cmd-dataframe",
plugin crate
2021-10-28 06:12:33 +00:00
"crates/nu-command",
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-11-02 15:18:57 +00:00
"crates/nu-lsp",
plugin crate
2021-10-28 06:12:33 +00:00
"crates/nu-protocol",
"crates/nu-plugin",
simple inc plugin implementation
2021-11-04 22:04:21 +00:00
"crates/nu_plugin_inc",
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 17:28:11 +00:00
"crates/nu_plugin_gstat",
Plugin with evaluated call (#393) * plugin trait * impl of trait * record and absolute path * plugin example crate * clippy error * correcting cargo * evaluated call for plugin
2021-12-02 05:42:56 +00:00
"crates/nu_plugin_example",
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 18:45:48 +00:00
"crates/nu_plugin_query",
Add CustomValue support to plugins (#6070) * Skeleton implementation Lots and lots of TODOs * Bootstrap simple CustomValue plugin support test * Create nu_plugin_custom_value * Skeleton for nu_plugin_custom_values * Return a custom value from plugin * Encode CustomValues from plugin calls as PluginResponse::PluginData * Add new PluginCall variant CollapseCustomValue * Handle CollapseCustomValue plugin calls * Add CallInput::Data variant to CallInfo inputs * Handle CallInfo with CallInput::Data plugin calls * Send CallInput::Data if Value is PluginCustomValue from plugin calls * Remove unnecessary boxing of plugins CallInfo * Add fields needed to collapse PluginCustomValue to it * Document PluginCustomValue and its purpose * Impl collapsing using plugin calls in PluginCustomValue::to_base_value * Implement proper typetag based deserialization for CoolCustomValue * Test demonstrating that passing back a custom value to plugin works * Added a failing test for describing plugin CustomValues * Support describe for PluginCustomValues - Add name to PluginResponse::PluginData - Also turn it into a struct for clarity - Add name to PluginCustomValue - Return name field from PluginCustomValue * Demonstrate that plugins can create and handle multiple CustomValues * Add bincode to nu-plugin dependencies This is for demonstration purposes, any schemaless binary seralization format will work. I picked bincode since it's the most popular for Rust but there are defintely better options out there for this usecase * serde_json::Value -> Vec<u8> * Update capnp schema for new CallInfo.input field * Move call_input capnp serialization and deserialization into new file * Deserialize Value's span from Value itself instead of passing call.head I am not sure if this was correct and I am breaking it or if it was a bug, I don't fully understand how nu creates and uses Spans. What should reuse spans and what should recreate new ones? But yeah it felt weird that the Value's Span was being ignored since in the json serializer just uses the Value's Span * Add call_info value round trip test * Add capnp CallInput::Data serialization and deserialization support * Add CallInfo::CollapseCustomValue to capnp schema * Add capnp PluginCall::CollapseCustomValue serialization and deserialization support * Add PluginResponse::PluginData to capnp schema * Add capnp PluginResponse::PluginData serialization and deserialization support * Switch plugins::custom_values tests to capnp Both json and capnp would work now! Sadly I can't choose both at the same time :( * Add missing JsonSerializer round trip tests * Handle plugin returning PluginData as a response to CollapseCustomValue * Refactor plugin calling into a reusable function Many less levels of indentation now! * Export PluginData from nu_plugin So plugins can create their very own serve_plugin with whatever CustomValue behavior they may desire * Error if CustomValue cannot be handled by Plugin
2022-07-25 16:32:56 +00:00
"crates/nu_plugin_custom_values",
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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 # 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-02-13 12:42:08 +00:00
"crates/nu_plugin_formats",
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs`
2023-04-07 20:12:27 +00:00
"crates/nu-std",
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 22:21:06 +00:00
"crates/nu-utils",
plugin crate
2021-10-28 06:12:33 +00:00
]
Add a few operators. Needs parser work
2021-08-25 19:29:36 +00:00
first commit
2021-06-30 01:42:56 +00:00
[dependencies]
Bump version to `0.86.1` (#10755) To dev or to patch that is the question
2023-10-18 18:00:51 +00:00
nu-cli = { path = "./crates/nu-cli", version = "0.86.1" }
nu-color-config = { path = "./crates/nu-color-config", version = "0.86.1" }
nu-cmd-base = { path = "./crates/nu-cmd-base", version = "0.86.1" }
nu-cmd-lang = { path = "./crates/nu-cmd-lang", version = "0.86.1" }
nu-cmd-dataframe = { path = "./crates/nu-cmd-dataframe", version = "0.86.1", features = ["dataframe"], optional = true }
nu-cmd-extra = { path = "./crates/nu-cmd-extra", version = "0.86.1", optional = true }
nu-command = { path = "./crates/nu-command", version = "0.86.1" }
nu-engine = { path = "./crates/nu-engine", version = "0.86.1" }
nu-explore = { path = "./crates/nu-explore", version = "0.86.1" }
nu-json = { path = "./crates/nu-json", version = "0.86.1" }
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-11-02 15:18:57 +00:00
nu-lsp = { path = "./crates/nu-lsp/", version = "0.86.1" }
Bump version to `0.86.1` (#10755) To dev or to patch that is the question
2023-10-18 18:00:51 +00:00
nu-parser = { path = "./crates/nu-parser", version = "0.86.1" }
nu-path = { path = "./crates/nu-path", version = "0.86.1" }
nu-plugin = { path = "./crates/nu-plugin", optional = true, version = "0.86.1" }
nu-pretty-hex = { path = "./crates/nu-pretty-hex", version = "0.86.1" }
nu-protocol = { path = "./crates/nu-protocol", version = "0.86.1" }
nu-system = { path = "./crates/nu-system", version = "0.86.1" }
nu-table = { path = "./crates/nu-table", version = "0.86.1" }
nu-term-grid = { path = "./crates/nu-term-grid", version = "0.86.1" }
nu-std = { path = "./crates/nu-std", version = "0.86.1" }
nu-utils = { path = "./crates/nu-utils", version = "0.86.1" }
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 11:16:18 +00:00
nu-ansi-term = "0.49.0"
Pin `reedline` to `0.25.0` release (#10741) See release notes: https://github.com/nushell/reedline/releases/tag/v0.25.0
2023-10-16 18:34:45 +00:00
reedline = { version = "0.25.0", features = ["bashisms", "sqlite"] }
add history session id to $nu (#6585) * add history session id to $nu * get nushell to compile * update test
2022-09-19 14:28:36 +00:00
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 00:22:25 +00:00
crossterm = "0.27"
Bump ctrlc from 3.3.1 to 3.4.0 (#9413)
2023-06-12 14:52:21 +00:00
ctrlc = "3.4"
remove unused dependencies (#9230) # Description This is a test PR to see if we can remove dependencies. The crates to remove was generated from cargo machete. If ci works, I'll update the PR to remove deps instead of comment them out. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-05-18 16:37:20 +00:00
log = "0.4"
Bump miette from 5.9.0 to 5.10.0 (#9713)
2023-07-17 06:25:04 +00:00
miette = { version = "5.10", features = ["fancy-no-backtrace"] }
bump nushell to dev version 0.84.1 (#10101) # Description This PR bumps nushell from release version 0.84.0 to dev version 0.84.1. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-08-23 20:23:27 +00:00
mimalloc = { version = "0.1.37", default-features = false, optional = true }
remove unused dependencies (#9230) # Description This is a test PR to see if we can remove dependencies. The crates to remove was generated from cargo machete. If ci works, I'll update the PR to remove deps instead of comment them out. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-05-18 16:37:20 +00:00
serde_json = "1.0"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-05-26 15:32:48 +00:00
simplelog = "0.12"
time = "0.3"
Add support for math-like externals (#4606)
2022-02-22 15:55:28 +00:00
Don't build OpenSSL on Windows (#5651)
2022-05-26 18:28:59 +00:00
[target.'cfg(not(target_os = "windows"))'.dependencies]
# Our dependencies don't use OpenSSL on Windows
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-05-26 15:32:48 +00:00
openssl = { version = "0.10", features = ["vendored"], optional = true }
signal-hook = { version = "0.3", default-features = false }
Don't build OpenSSL on Windows (#5651)
2022-05-26 18:28:59 +00:00
Upgrade reedline to latest dev version (#6778) * Reorder conditional deps for readability * Pull reedline from the most recent main branch * Map 'Submit' and 'SubmitOrNewline' events Introduced by nushell/reedline#490
2022-10-16 21:51:15 +00:00
[target.'cfg(windows)'.build-dependencies]
Move from `winres` to better-maintained `winresource` fork (#9001) This MR closes #8986; big thanks to @WindSoilder for investigating this and making the MR very easy. I did manual testing to confirm that the icon etc. are still being set correctly after this change. Also skimmed the `winresource` code, no issues jumped out at me.
2023-04-26 12:14:55 +00:00
winresource = "0.1"
Upgrade reedline to latest dev version (#6778) * Reorder conditional deps for readability * Pull reedline from the most recent main branch * Map 'Submit' and 'SubmitOrNewline' events Introduced by nushell/reedline#490
2022-10-16 21:51:15 +00:00
[target.'cfg(target_family = "unix")'.dependencies]
upgrade nix to 0.27 (#10223) This fixes a segfault on Android when fetching the user group. See: https://github.com/nix-rust/nix/issues/2084
2023-09-04 20:41:28 +00:00
nix = { version = "0.27", default-features = false, features = [
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 12:32:20 +00:00
"signal",
"process",
"fs",
"term",
] }
Upgrade reedline to latest dev version (#6778) * Reorder conditional deps for readability * Pull reedline from the most recent main branch * Map 'Submit' and 'SubmitOrNewline' events Introduced by nushell/reedline#490
2022-10-16 21:51:15 +00:00
add more tests
2021-07-30 20:02:16 +00:00
[dev-dependencies]
Bump version to `0.86.1` (#10755) To dev or to patch that is the question
2023-10-18 18:00:51 +00:00
nu-test-support = { path = "./crates/nu-test-support", version = "0.86.1" }
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-05-26 15:32:48 +00:00
assert_cmd = "2.0"
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 13:29:54 +00:00
criterion = "0.5"
Bump pretty_assertions from 1.3.0 to 1.4.0 (#9781)
2023-07-24 05:41:03 +00:00
pretty_assertions = "1.4"
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 17:11:05 +00:00
rstest = { version = "0.18", default-features = false }
update to current reedline (#9877) # Description This PR updates nushell to use the latest reedline. I swear that was the only change I made. The other reordering stuff is by my vscode extension I guess. closes https://github.com/nushell/nushell/issues/9123 # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-08-01 20:30:31 +00:00
serial_test = "2.0"
Bump tempfile from 3.7.0 to 3.8.0 (#10307)
2023-09-11 09:54:49 +00:00
tempfile = "3.8"
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
[features]
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 18:57:40 +00:00
plugin = [
"nu-plugin",
"nu-cli/plugin",
"nu-parser/plugin",
"nu-command/plugin",
"nu-protocol/plugin",
"nu-engine/plugin",
]
Adds mimalloc as default feature. (#10378) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> This PR makes `mimalloc` the default allocator, it has been the default on the nightly builds of nushell now for a couple of months and the performance improvements are quite nice, measuring upwards of 30% faster startup time on Windows, and a bit smaller on Linux, https://github.com/nushell/nushell/pull/9415 # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-09-15 19:17:33 +00:00
default = ["plugin", "which-support", "trash-support", "sqlite", "mimalloc"]
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
stable = ["default"]
Fix version to show build features after crateification (#9262) # Description Addresses missing features per #9261 # User-Facing Changes Fixes output of version. Adds wasi feature output # Tests + Formatting No tests written Co-authored-by: Robert Waugh <robert@waugh.io>
2023-05-22 15:42:38 +00:00
wasi = ["nu-cmd-lang/wasi"]
Break up interdependencies of command crates (#9429) # Description Make sure that our different crates that contain commands can be compiled in parallel. This can under certain circumstances accelerate the compilation with sufficient multithreading available. ## Details - Move `help` commands from `nu-cmd-lang` back to `nu-command` - This also makes sense as the commands are implemented in an ANSI-terminal specific way - Make `nu-cmd-lang` only a dev dependency for `nu-command` - Change context creation helpers for `nu-cmd-extra` and `nu-cmd-dataframe` to have a consistent api used in `src/main.rs`:`get_engine_state()` - `nu-command` now indepedent from `nu-cmd-extra` and `nu-cmd-dataframe` that are now dependencies of `nu` directly. (change to internal features) - Fix tests that previously used `nu-command::create_default_context()` with replacement functions ## From scratch compilation times: just debug (dev) build and default features ``` cargo clean --profile dev && cargo build --timings ``` ### before ![grafik](https://github.com/nushell/nushell/assets/15833959/e49f1f42-2e53-4a6c-bc23-625b686af1bc) ### after ![grafik](https://github.com/nushell/nushell/assets/15833959/8dec4723-e625-4a86-b91e-e6e808f64726) # User-Facing Changes None direct, only change to compilation on multithreaded jobs expected. # Tests + Formatting Tests that previously chose to use `nu-command` for their scope will still use `nu-cmd-lang` + `nu-command` (command list in the granularity at the time)
2023-06-14 21:12:55 +00:00
# NOTE: individual features are also passed to `nu-cmd-lang` that uses them to generate the feature matrix in the `version` command
Move dataframe out of extra (#7180)
2022-11-21 17:24:25 +00:00
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **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. -->
2023-10-10 23:13:28 +00:00
# Enable to statically link OpenSSL (perl is required, to build OpenSSL https://docs.rs/openssl/latest/openssl/);
Mention that perl is required for feature static-link-openssl… (#10291) this PR should close https://github.com/nushell/nushell/issues/10290 it is a simple comment in Cargo.toml, which explains that perl is required for feature static-link-openssl to work.
2023-09-09 20:34:07 +00:00
# otherwise the system version will be used. Not enabled by default because it takes a while to build
Fix version to show build features after crateification (#9262) # Description Addresses missing features per #9261 # User-Facing Changes Fixes output of version. Adds wasi feature output # Tests + Formatting No tests written Co-authored-by: Robert Waugh <robert@waugh.io>
2023-05-22 15:42:38 +00:00
static-link-openssl = ["dep:openssl", "nu-cmd-lang/static-link-openssl"]
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
Changes global allocator to mimalloc, improving performance. (#9415) # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > **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. -->
2023-06-14 22:27:12 +00:00
mimalloc = ["nu-cmd-lang/mimalloc", "dep:mimalloc"]
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
# Stable (Default)
Fix version to show build features after crateification (#9262) # Description Addresses missing features per #9261 # User-Facing Changes Fixes output of version. Adds wasi feature output # Tests + Formatting No tests written Co-authored-by: Robert Waugh <robert@waugh.io>
2023-05-22 15:42:38 +00:00
which-support = ["nu-command/which-support", "nu-cmd-lang/which-support"]
trash-support = ["nu-command/trash-support", "nu-cmd-lang/trash-support"]
Add `which` command, add external completions, and builtin var completions (#782) * Add which and external completions * WIP * Finish up external and var completions * fix windows
2022-01-20 18:02:53 +00:00
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 17:46:16 +00:00
# Extra feature for nushell
Break up interdependencies of command crates (#9429) # Description Make sure that our different crates that contain commands can be compiled in parallel. This can under certain circumstances accelerate the compilation with sufficient multithreading available. ## Details - Move `help` commands from `nu-cmd-lang` back to `nu-command` - This also makes sense as the commands are implemented in an ANSI-terminal specific way - Make `nu-cmd-lang` only a dev dependency for `nu-command` - Change context creation helpers for `nu-cmd-extra` and `nu-cmd-dataframe` to have a consistent api used in `src/main.rs`:`get_engine_state()` - `nu-command` now indepedent from `nu-cmd-extra` and `nu-cmd-dataframe` that are now dependencies of `nu` directly. (change to internal features) - Fix tests that previously used `nu-command::create_default_context()` with replacement functions ## From scratch compilation times: just debug (dev) build and default features ``` cargo clean --profile dev && cargo build --timings ``` ### before ![grafik](https://github.com/nushell/nushell/assets/15833959/e49f1f42-2e53-4a6c-bc23-625b686af1bc) ### after ![grafik](https://github.com/nushell/nushell/assets/15833959/8dec4723-e625-4a86-b91e-e6e808f64726) # User-Facing Changes None direct, only change to compilation on multithreaded jobs expected. # Tests + Formatting Tests that previously chose to use `nu-command` for their scope will still use `nu-cmd-lang` + `nu-command` (command list in the granularity at the time)
2023-06-14 21:12:55 +00:00
extra = ["dep:nu-cmd-extra", "nu-cmd-lang/extra"]
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 01:16:35 +00:00
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
# Dataframe feature for nushell
Break up interdependencies of command crates (#9429) # Description Make sure that our different crates that contain commands can be compiled in parallel. This can under certain circumstances accelerate the compilation with sufficient multithreading available. ## Details - Move `help` commands from `nu-cmd-lang` back to `nu-command` - This also makes sense as the commands are implemented in an ANSI-terminal specific way - Make `nu-cmd-lang` only a dev dependency for `nu-command` - Change context creation helpers for `nu-cmd-extra` and `nu-cmd-dataframe` to have a consistent api used in `src/main.rs`:`get_engine_state()` - `nu-command` now indepedent from `nu-cmd-extra` and `nu-cmd-dataframe` that are now dependencies of `nu` directly. (change to internal features) - Fix tests that previously used `nu-command::create_default_context()` with replacement functions ## From scratch compilation times: just debug (dev) build and default features ``` cargo clean --profile dev && cargo build --timings ``` ### before ![grafik](https://github.com/nushell/nushell/assets/15833959/e49f1f42-2e53-4a6c-bc23-625b686af1bc) ### after ![grafik](https://github.com/nushell/nushell/assets/15833959/8dec4723-e625-4a86-b91e-e6e808f64726) # User-Facing Changes None direct, only change to compilation on multithreaded jobs expected. # Tests + Formatting Tests that previously chose to use `nu-command` for their scope will still use `nu-cmd-lang` + `nu-command` (command list in the granularity at the time)
2023-06-14 21:12:55 +00:00
dataframe = ["dep:nu-cmd-dataframe", "nu-cmd-lang/dataframe"]
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
Feature cleanup (#7182) Following up on #7180 with some feature cleanup: - Move the `database` feature from `plugin` to `default` - Rename the `database` feature to `sqlite` - Remove `--features=extra` from a lot of scripts etc. - No need to specify this, the `extra` feature is now the same as the default feature set - Remove the now-redundant 2nd Ubuntu test run
2022-11-23 00:58:11 +00:00
# SQLite commands for nushell
Fix version to show build features after crateification (#9262) # Description Addresses missing features per #9261 # User-Facing Changes Fixes output of version. Adds wasi feature output # Tests + Formatting No tests written Co-authored-by: Robert Waugh <robert@waugh.io>
2023-05-22 15:42:38 +00:00
sqlite = ["nu-command/sqlite", "nu-cmd-lang/sqlite"]
Database commands (#5307) * database commands * db commands * filesystem opens sqlite file * clippy error * corrected error in ci file * removes matrix flag from ci * flax matrix for clippy * add conditional compile for tests * add conditional compile for tests * correct order of command * correct error msg * correct typo
2022-04-24 09:29:21 +00:00
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
[profile.release]
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 18:57:40 +00:00
opt-level = "s" # Optimize for size
Add profiling build profile and symbol strip (#4630) * Add profiling build profile and symbol strip Stripping the symbols for the release build improves the size of the binary significantly Adds a custom build profile for performance profiling that includes all symbols for analysis. Can be used via ``` cargo build --profile profiling ``` * Retain a minimal backtrace
2022-02-28 12:13:24 +00:00
strip = "debuginfo"
reorganize features a bit (#4807)
2022-03-10 13:37:24 +00:00
lto = "thin"
Add profiling build profile and symbol strip (#4630) * Add profiling build profile and symbol strip Stripping the symbols for the release build improves the size of the binary significantly Adds a custom build profile for performance profiling that includes all symbols for analysis. Can be used via ``` cargo build --profile profiling ``` * Retain a minimal backtrace
2022-02-28 12:13:24 +00:00
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 22:21:06 +00:00
# build with `cargo build --profile profiling`
Add profiling build profile and symbol strip (#4630) * Add profiling build profile and symbol strip Stripping the symbols for the release build improves the size of the binary significantly Adds a custom build profile for performance profiling that includes all symbols for analysis. Can be used via ``` cargo build --profile profiling ``` * Retain a minimal backtrace
2022-02-28 12:13:24 +00:00
# to analyze performance with tooling like linux perf
[profile.profiling]
inherits = "release"
strip = false
debug = true
enable `cargo build --features=extra` to build plugins (#448)
2021-12-07 20:06:34 +00:00
Try removing debuginfo for ci builds (#5549) * Try removing debuginfo for ci builds * oops, wrong inherits * extra flag * nextest doesn't support --profile in the same way * try to allow for a ci-specific target * Oops, run more tests
2022-05-16 04:02:11 +00:00
# build with `cargo build --profile ci`
# to analyze performance with tooling like linux perf
[profile.ci]
inherits = "dev"
strip = false
debug = false
Move some plugins back to being core shippable plugins
2019-12-10 00:05:40 +00:00
# Main nu binary
First working plugin
2019-06-27 04:56:48 +00:00
[[bin]]
name = "nu"
path = "src/main.rs"
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 22:22:00 +00:00
bench = false
Foreground process group management, again (#6584) * Revert "Revert "Try again: in unix like system, set foreground process while running external command (#6273)" (#6542)" This reverts commit 2bb367f570502cd26d6b7a81425d9f3b3b9eb432. * Make foreground job control hopefully work correctly These changes are mostly inspired by the glibc manual. * Fix typo in external command description * Only restore tty control to shell when no fg procs are left; reuse pgrp * Rework terminal acquirement code to be like fish Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-09-29 18:37:48 +00:00
Pin reedline to the 0.13.0 release (#6789) See the release notes: https://github.com/nushell/reedline/releases/tag/v0.13.0
2022-10-17 21:45:28 +00:00
# To use a development version of a dependency please use a global override here
# changing versions in each sub-crate of the workspace is tedious
Upgrade reedline to latest dev version (#6778) * Reorder conditional deps for readability * Pull reedline from the most recent main branch * Map 'Submit' and 'SubmitOrNewline' events Introduced by nushell/reedline#490
2022-10-16 21:51:15 +00:00
[patch.crates-io]
Make hints aware of the current directory (#10780) This commit uses the new `CwdAwareHinter` in reedline. Closes #8883. # Description Currently, the history based hints show results from all directories, while most commands make sense only in the directory they were run in. This PR makes hints take the current directory into account. # User-Facing Changes Described above. I haven't yet added a config option for this, because I personally believe folks won't be against it once they try it out. We can add it if people complain, there's some time before the next release. Fish has this without a config option too. # Tests + Formatting If tests are needed, I'll need help as I'm not well versed with the codebase.
2023-10-20 09:21:58 +00:00
reedline = { git = "https://github.com/nushell/reedline.git", branch = "main" }
Pin to `nu-ansi-term` 0.47 (#8440) # Description Update reedline to a commit that uses the same version as we share types # User-Facing Changes (-) # Tests + Formatting Build check
2023-03-13 22:38:18 +00:00
# nu-ansi-term = {git = "https://github.com/nushell/nu-ansi-term.git", branch = "main"}
Pin `uu_cp` to the `0.0.22` release. (#10725)
2023-10-15 19:19:34 +00:00
# uu_cp = { git = "https://github.com/uutils/coreutils.git", branch = "main" }
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 19:39:54 +00:00
# Criterion benchmarking setup
# Run all benchmarks with `cargo bench`
# Run individual benchmarks like `cargo bench -- <regex>` e.g. `cargo bench -- parse`
[[bench]]
Combine benchmarks to speed up `cargo bench` build times (#7722) I've been using the new Criterion benchmarks and I noticed that they take a _long_ time to build before the benchmark can run. Turns out `cargo build` was building 3 separate benchmarking binaries with most of Nu's functionality in each one. As a simple temporary fix, I've moved all the benchmarks into a single file so that we only build 1 binary. ### Future work Would be nice to split the unrelated benchmarks out into modules, but when I did that a separate binary still got built for each one. I suspect Criterion's macros are doing something funny with module or file names. I've left a FIXME in the code to investigate this further.
2023-01-11 01:51:25 +00:00
name = "benchmarks"
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 18:57:40 +00:00
harness = false
Reference in a new issue Copy permalink