extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-10-17 15:52:50 +02:00
Code Issues Packages Projects Releases Wiki Activity
1943071d12
nushell/crates/nu-completion/Cargo.toml

30 lines
845 B
TOML
Raw Normal View History

Extract completions into subcrate. (#3631)
2021-06-16 22:20:01 +02:00
[package]
authors = ["The Nu Project Contributors"]
description = "Completions for nushell"
edition = "2018"
license = "MIT"
name = "nu-completion"
Bump to 0.33.1 (#3671)
2021-06-23 09:57:41 +02:00
version = "0.33.1"
Extract completions into subcrate. (#3631)
2021-06-16 22:20:01 +02:00
[lib]
doctest = false
[dependencies]
Bump to 0.33.1 (#3671)
2021-06-23 09:57:41 +02:00
nu-engine = { version="0.33.1", path="../nu-engine" }
nu-data = { version="0.33.1", path="../nu-data" }
nu-errors = { version="0.33.1", path="../nu-errors" }
nu-parser = { version="0.33.1", path="../nu-parser" }
nu-path = { version="0.33.1", path="../nu-path" }
nu-protocol = { version="0.33.1", path="../nu-protocol" }
nu-source = { version="0.33.1", path="../nu-source" }
nu-test-support = { version="0.33.1", path="../nu-test-support" }
Extract completions into subcrate. (#3631)
2021-06-16 22:20:01 +02:00
Remove dir-s/ectories/ectories-support features (#3647)
2021-06-19 01:29:29 +02:00
dirs-next = "2.0.0"
Bump to 0.33.1 (#3671)
2021-06-23 09:57:41 +02:00
indexmap = { version="1.6.1", features=["serde-1"] }
Simplify `is_executable` in `nu-completion`. (#3742) On Windows, we used the `is-exeuctable` crate but on Unix, we duplicated the check that it did, with one difference: We also looked at whether or not it was a symlink. The `is-executable` crate uses `std::fs::metadata` which follows symlinks, so this scenario should never occur here, as it will return the metadata for the target file. Using the `is-executable` crate on both Unix and Windows lets us make it non-optional. This lets us remove the `executable-support` feature. (It is worth noting that this code didn't compile on Windows when the `executable-support` feature was not specified.) Right now, there is an alternate code path for `target_arch` being `wasm32`. This isn't exactly correct as it should probably handle something different for when the `target_os` is `wasi`.
2021-07-07 14:53:07 +02:00
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
is_executable = "1.0.1"
Variable completions. (#3666) In Nu we have variables (E.g. $var-name) and these contain `Value` types. This means we can bind to variables any structured data and column path syntax (E.g. `$variable.path.to`) allows flexibility for "querying" said structures. Here we offer completions for these. For example, in a Nushell session the variable `$nu` contains environment values among other things. If we wanted to see in the screen some environment variable (say the var `SHELL`) we do: ``` > echo $nu.env.SHELL ``` with completions we can now do: `echo $nu.env.S[\TAB]` and we get suggestions that start at the column path `$nu.env` with vars starting with the letter `S` in this case `SHELL` appears in the suggestions.
2021-06-23 09:21:39 +02:00
[dev-dependencies]
parking_lot = "0.11.1"
Reference in New Issue Copy Permalink