mirror of
https://github.com/nushell/nushell.git
synced 2025-06-08 19:17:16 +02:00
- fixes #15731 # Description Existing bare word string interpolation only works if the string doesn't start with a subxpression. ```nushell echo fork(2) # => fork2 echo (2)fork # => Error: nu::parser::unclosed_delimiter # => # => × Unclosed delimiter. # => ╭─[entry #25:1:13] # => 1 │ echo (2)fork # => ╰──── ``` This PR lifts that restriction. ```nushell echo fork(2) # => fork2 echo (2)fork # => 2fork ``` This was first brought to my attention on discord with the following command failing to parse. ```nushell docker run -u (id -u):(id -g) ``` It now works. # User-Facing Changes # Tests + Formatting No existing test broke or required tweaking. Additional tests covering this case was added. - 🟢 toolkit fmt - 🟢 toolkit clippy - 🟢 toolkit test - 🟢 toolkit test stdlib # After Submitting --------- Co-authored-by: Bahex <17417311+Bahex@users.noreply.github.com>
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.