nushell/crates/nu-command
Bruce Mitchener 651d425046
Remove ptree dep from nu-command, remove associated feature. (#3741)
Nothing used the `ptree` feature or optional dependency within
`nu-command` except to include it within the `version` output. This
may be related to when `nu-cli` also had a `ptree` feature, but
I'm not sure.

That leaves the code within `nu_plugin_tree` as the sole remaining
user of `ptree`, which is already covered by the feature `tree`
and included in the `version` output.
2021-07-06 10:33:24 -05:00
..
assets nu-cli refactor moving commands into their own crate nu-command (#2910) 2021-01-12 17:59:53 +13:00
src Remove ptree dep from nu-command, remove associated feature. (#3741) 2021-07-06 10:33:24 -05:00
tests nu-cli: Remove crates not needed. (#3716) 2021-06-30 17:47:56 -05:00
build.rs nu-cli refactor moving commands into their own crate nu-command (#2910) 2021-01-12 17:59:53 +13:00
Cargo.toml Remove ptree dep from nu-command, remove associated feature. (#3741) 2021-07-06 10:33:24 -05:00
README.md Begin directory contrib docs and split commands (#3650) 2021-06-19 12:06:44 +12:00

nu-command

The Nu command crate contains the full set of internal commands, that is, the commands that can be form the set of built-in commands in a Nushell engine.

The default set of commands that Nushell ships with can be found in the default context.

The commands themselves live in the commands module.