forked from extern/nushell
249afc5df4
I noticed that the help for the `url` command was confusing (it wasn't clear that `url` is just a base command that does nothing itself) and the input type was also wrong. Fixed. Before: ```bash 〉help url Apply url function. Search terms: network, parse Usage: > url Subcommands: url parse - Parses a url Flags: -h, --help - Display the help message for this command Signatures: <string> | url -> <string> ``` After: ```bash 〉help url Various commands for working with URLs You must use one of the following subcommands. Using this command as-is will only produce this help message. Search terms: network, parse Usage: > url Subcommands: url parse - Parses a url Flags: -h, --help - Display the help message for this command Signatures: <nothing> | url -> <string> ``` |
||
---|---|---|
.. | ||
nu_plugin_custom_values | ||
nu_plugin_example | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu-cli | ||
nu-color-config | ||
nu-command | ||
nu-engine | ||
nu-explore | ||
nu-glob | ||
nu-json | ||
nu-parser | ||
nu-path | ||
nu-plugin | ||
nu-pretty-hex | ||
nu-protocol | ||
nu-system | ||
nu-table | ||
nu-term-grid | ||
nu-test-support | ||
nu-utils | ||
README.md |
Nushell core libraries and plugins
These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.
Foundational libraries are split into two kinds of crates:
- Core crates - those crates that work together to build the Nushell language engine
- Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.
Plugins are likewise also split into two types:
- Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
- Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.