mirror of
https://github.com/nushell/nushell.git
synced 2024-10-16 15:22:43 +02:00
7c274ad4d8
This PR removes the `line_head_top`, `line_head_bottom`, `line_shift`, and `line_index` configuration options from `explore`. These were previously used to control whether the horizontal+vertical lines in this `ls | explore -i` screenshot would be displayed:  Now, all lines are displayed (same as the previous default config values) and this is no longer configurable. ## Context I'm continuing to chip away at `explore` when I have time. I have a long-term goal to make `explore` simpler for users+developers. For now I'm mostly making small incremental changes where I find underused functionality+configuration and remove it; hopefully eventually this will make it easier to make larger changes. I found these specific config options a little hard to understand when reading `explore` code, and when reading `config.nu` as a user their behaviour+naming is not obvious. I also think that in the long term, `explore` styling should inherit most styling from `table` instead of having its own styling system. |
||
|---|---|---|
| .. | ||
| 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-base | ||
| nu-cmd-dataframe | ||
| nu-cmd-extra | ||
| 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.