forked from extern/nushell
19c3570cf9
* Remove panic from BlockCommands run function Instead of panicing, the run method now returns an error to prevent nushell from unexpected termination. * Add ability to open command to run with blocks The open command tries to parse the content of the file if there is a command called 'from (file ending)'. This works fine if the command was 'built in' because the run method doesn't fail in this case. It did fail on a BlockCommand, though. This change will first probe if the command contains a block and evaluate it, if this is the case. If there is no block, it will run the command the same way as before. * Add test open files with BlockCommands * Update open.rs * Adjust file type on open with BlockCommand parser Co-authored-by: JT <547158+jntrnr@users.noreply.github.com> |
||
---|---|---|
.. | ||
nu_plugin_example | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu-cli | ||
nu-color-config | ||
nu-command | ||
nu-engine | ||
nu-glob | ||
nu-json | ||
nu-parser | ||
nu-path | ||
nu-plugin | ||
nu-pretty-hex | ||
nu-protocol | ||
nu-system | ||
nu-table | ||
nu-term-grid | ||
nu-test-support | ||
nu-utils | ||
old | ||
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.