forked from extern/nushell
1794ad51bd
* fix #4140 We are passing commands into a shell underneath but we were not escaping arguments correctly. This new version of the code also takes into consideration the ";" and "&" characters, which have special meaning in shells. We would probably benefit from a more robust way to join arguments to shell programs. Python's stdlib has shlex.join, and perhaps we can take that implementation as a reference. * clean up escaping of posix shell args I believe the right place to do escaping of arguments was in the spawn_sh_command function. Note that this change prevents things like: ^echo "$(ls)" from executing the ls command. Instead, this will just print $(ls) The regex has been taken from the python stdlib implementation of shlex.quote * fix non-literal parameters and single quotes * address clippy's comments * fixup! address clippy's comments * test that subshell commands are sanitized properly |
||
|---|---|---|
| .. | ||
| nu_plugin_binaryview | ||
| nu_plugin_chart | ||
| nu_plugin_from_bson | ||
| nu_plugin_from_mp4 | ||
| nu_plugin_from_sqlite | ||
| nu_plugin_inc | ||
| nu_plugin_match | ||
| nu_plugin_query_json | ||
| nu_plugin_s3 | ||
| nu_plugin_selector | ||
| nu_plugin_start | ||
| nu_plugin_textview | ||
| nu_plugin_to_bson | ||
| nu_plugin_to_sqlite | ||
| nu_plugin_tree | ||
| nu_plugin_xpath | ||
| nu-ansi-term | ||
| nu-cli | ||
| nu-command | ||
| nu-completion | ||
| nu-data | ||
| nu-engine | ||
| nu-errors | ||
| nu-json | ||
| nu-parser | ||
| nu-path | ||
| nu-plugin | ||
| nu-pretty-hex | ||
| nu-protocol | ||
| nu-serde | ||
| nu-source | ||
| nu-stream | ||
| nu-table | ||
| nu-test-support | ||
| nu-value-ext | ||
| 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.