mirror of
https://github.com/nushell/nushell.git
synced 2025-05-16 16:04:30 +02:00
80788636ee
# Description This PR removes the old `touch` command in favor of the uutils/coreutils implementation of `touch`, which we integrated in 0.101 (#11817). It turns out that in `utouch`, the `--no-deref`/`-s` wasn't working, and the issue had gone undetected because I accidentally made the test for that use `touch` rather than `utouch`. This has been fixed now. # User-Facing Changes Our old `touch` command didn't have anything that the new uutils-based command doesn't, and the uutils-based command actually has a little more functionality. So nothing using `touch` should break. Scripts using `utouch` will have to use `touch` now, but given that `utouch` has been around for less than 2 months, I assume people haven't really been using it. # Tests + Formatting The utouch tests seem to have everything from the old touch tests, so I deleted the old touch tests. # After Submitting This will need to be mentioned in the release notes. |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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 | ||
| 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.