mirror of
https://github.com/nushell/nushell
synced 2024-12-26 04:53:09 +00:00
186c08467f
# Description Fixes: #13159 After the change, `std help` will no-longer print out "double error" messages. Actually I think it's tricky to make it right. To make `help <cmd>` keeps paging feature from fallback `man` command. I have to split `commands` into `scope-commands` and `external-commands`. If we don't split it, simply call `let commands = (try { commands $target_item --find $find })` in `help main` will cause us to lost paging feature, which is not we want. A comment from original issue: > If there are no objections, I'd like to remove the man page fallback code from std help for the moment. While it's probably fixable, it's also platform specific and requires testing on all platforms. It also seems like a low-value add here. Actually I think it's a beautiful feature of `std help`, so I want to keep it here. # User-Facing Changes ### Before ```nushell > help commands asdfadsf Help pages from external command asdfadsf: No manual entry for asdfadsf Error: × std::help::command_not_found ╭─[entry #11:1:15] 1 │ help commands asdfadsf · ────┬─── · ╰── command not found ╰──── ``` ### After ```nushell > help commands asdfasdf Help pages from external command asdfasdf: No manual entry for asdfasdf ``` # Tests + Formatting Actually it's a little hard to add test because it required user input (especially for fallback `man` command) |
||
|---|---|---|
| .. | ||
| nu-cli | ||
| nu-cmd-base | ||
| nu-cmd-extra | ||
| nu-cmd-lang | ||
| nu-cmd-plugin | ||
| nu-color-config | ||
| nu-command | ||
| nu-derive-value | ||
| nu-engine | ||
| nu-explore | ||
| nu-glob | ||
| nu-json | ||
| nu-lsp | ||
| nu-parser | ||
| nu-path | ||
| nu-plugin | ||
| nu-plugin-core | ||
| nu-plugin-engine | ||
| nu-plugin-protocol | ||
| nu-plugin-test-support | ||
| nu-pretty-hex | ||
| nu-protocol | ||
| nu-std | ||
| nu-system | ||
| nu-table | ||
| nu-term-grid | ||
| nu-test-support | ||
| nu-utils | ||
| nu_plugin_custom_values | ||
| nu_plugin_example | ||
| nu_plugin_formats | ||
| nu_plugin_gstat | ||
| nu_plugin_inc | ||
| nu_plugin_nu_example | ||
| nu_plugin_polars | ||
| nu_plugin_python | ||
| nu_plugin_query | ||
| nu_plugin_stress_internals | ||
| nuon | ||
| 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.