forked from extern/nushell
03c9eaf005
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.
28 lines
818 B
TOML
28 lines
818 B
TOML
[package]
|
|
authors = ["The Nu Project Contributors"]
|
|
description = "Completions for nushell"
|
|
edition = "2018"
|
|
license = "MIT"
|
|
name = "nu-completion"
|
|
version = "0.33.0"
|
|
|
|
[lib]
|
|
doctest = false
|
|
|
|
[dependencies]
|
|
nu-engine = { version="0.33.0", path="../nu-engine" }
|
|
nu-data = { version="0.33.0", path="../nu-data" }
|
|
nu-errors = { version="0.33.0", path="../nu-errors" }
|
|
nu-parser = { version="0.33.0", path="../nu-parser" }
|
|
nu-path = { version="0.33.0", path="../nu-path" }
|
|
nu-protocol = { version="0.33.0", path="../nu-protocol" }
|
|
nu-source = { version="0.33.0", path="../nu-source" }
|
|
nu-test-support = { version="0.33.0", path="../nu-test-support" }
|
|
|
|
dirs-next = "2.0.0"
|
|
indexmap = { version = "1.6.1", features = ["serde-1"] }
|
|
is_executable = { version="1.0.1", optional=true }
|
|
|
|
[dev-dependencies]
|
|
parking_lot = "0.11.1"
|