nushell

mirror of https://github.com/nushell/nushell.git synced 2024-12-30 19:09:15 +01:00

History

Andrés N. Robalino 03c9eaf005 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 19:21:39 +12:00
..
src	Variable completions. (#3666 )	2021-06-23 19:21:39 +12:00
Cargo.toml	Bump to 0.33 (#3667 )	2021-06-22 17:22:33 +12:00

Andrés N. Robalino 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.

2021-06-23 19:21:39 +12:00

src

Variable completions. (#3666 )

2021-06-23 19:21:39 +12:00

Cargo.toml

Bump to 0.33 (#3667 )

2021-06-22 17:22:33 +12:00