mirror of
https://github.com/nushell/nushell.git
synced 2025-07-12 12:26:05 +02:00
a6b8e2f95c
Closes: https://github.com/nushell/nushell/issues/13127 # Description This PR updates the behaviour of `start` in the following ways: Instead of joining the path with CWD, we expand the path. Behaviour on `origin/main`: ``` nushell> ls ~/nushell-test test.txt nushell> start ~/nushell-test/test.txt Error: × Cannot find file or URL: ~/nushell-test/test.txt ... help: Ensure the path or URL is correct and try again. ``` Behaviour in this PR: ``` nushell> ls ~/nushell-test test.txt nushell> start ~/nushell-test/test.txt <opens text editor> ``` # User-Facing Changes `start` now treats the input path differently. This is a breaking change, I believe. Although I'm not sure how breaking it would be in the perspective of the user. # Tests + Formatting I've manually tested this. The test suite for `start` is broken. And even if I fix it, I'm not sure how to test it. I'll need to override the default command list for `start` in the sandbox for testing. # After Submitting I don't think the documentation needs to be updated.
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.