forked from extern/nushell
651d425046
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. |
||
|---|---|---|
| .. | ||
| assets | ||
| src | ||
| tests | ||
| build.rs | ||
| Cargo.toml | ||
| README.md | ||
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.