forked from extern/nushell
36036d9308
# Description i was playing with my theme a bit and i was thinking about the following - the default themes should not use precise colors - the default themes should let the terminal set the exact colors for instance, the `filesize` field of the `$env.config.color_config` looks good but not with terminal themes like dracula or tokyonight 😮 in this PR, i just use "built-in" colors, like `red` or `yellow_bold` or `{fg: green attr: n}` to let the terminal theme set the colors 😋 # User-Facing Changes i tried to stay as close as the previous default themes, so there should be the least amount of differences 😌 # Tests + Formatting ``` $nothing ``` # 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-std | ||
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.