mirror of
https://github.com/nushell/nushell.git
synced 2025-02-24 22:41:54 +01:00
# Description fixed #8655 Change default nushell configuration file `default_env.nu` to display LAST_EXIT_CODE in the prompt. For this change, users can quickly know that a previous command failed. # User-Facing Changes This change affects only users who use the default configuration. When a command fails, the exit code is displayed in the prompt like these figures. * before  * after  # Tests + Formatting When I ran tests, `test.nu` failed with the following error. The error also occurs in the master branch, so it's probably unrelated to these changes. Do I need to address it? * `cargo fmt --all -- --check`: passed * `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect`: passed * `cargo test --workspace`: passed * `cargo run -- crates/nu-utils/standard_library/tests.nu`: ~failed~ passed ``` ~/oss_dev/nushell> cargo run -- crates/nu-utils/standard_library/tests.nu Finished dev [unoptimized + debuginfo] target(s) in 0.15s Running `target/debug/nu crates/nu-utils/standard_library/tests.nu` Error: nu:🐚:external_command × External command failed ╭─[/home/hiroki/oss_dev/nushell/crates/nu-utils/standard_library/tests.nu:73:1] 73 │ | upsert test {|module| 74 │ nu -c $'use ($module.file) *; $nu.scope.commands | select name module_name | to nuon' · ─┬ · ╰── did you mean 'du'? 75 │ | from nuon ╰──── help: No such file or directory (os error 2) ``` # After Submitting nothing |
||
---|---|---|
.. | ||
nu_plugin_custom_values | ||
nu_plugin_example | ||
nu_plugin_formats | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu-cli | ||
nu-cmd-lang | ||
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.