Stefan Holderbach 944ebac1c2
Eliminate dead code in nu-explore (#12735)
# Description
Nightly clippy found some unused fields leading me down a rabbit hole of
dead code hidden behind `pub`

Generally removing any already dead code or premature configurability
that is not exposed to the user.

# User-Facing Changes

None in effect.

Removed some options from the `$env.config.explore.hex-dump` record that
were only read into a struct but never used and also not validated.
2024-05-03 08:36:58 +08:00
..
2024-05-03 08:36:10 +08:00
2024-05-03 08:36:10 +08:00
2024-05-03 08:36:10 +08:00
2024-05-01 17:19:20 -05:00
2024-05-01 17:19:20 -05:00
2024-05-03 08:36:10 +08:00
2024-05-03 08:36:10 +08:00
2024-05-01 17:19:20 -05:00
2024-05-01 17:19:20 -05:00
2024-05-03 08:36:10 +08:00
2022-02-07 14:54:06 -05:00

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.