If the plugin is a filter, data streams to it one element at a time, and it can stream data back in return via stdin/stdout. These binaries interact with nu via a simple JSON-RPC protocol where the command identifies itself and passes along its configuration, making it available for use. Plugins are binaries that are available in your path and follow a nu_plugin_* naming convention. There are a few examples in the crates/nu_plugins_* directories. Nu supports plugins that offer additional functionality to the shell and follow the same structured data model that built-in commands use. Commands that consume the output of the pipeline (e.g., table)Ĭommands are separated by the pipe symbol ( |) to denote a pipeline flowing left to right.Commands that filter a stream (e.g., where type = "dir").Commands that produce a stream (e.g., ls).Nu takes this a step further and builds heavily on the idea of pipelines.Īs in the Unix philosophy, Nu allows commands to output to stdout and read from stdin.Īdditionally, commands can output structured data (you can think of this as a third kind of stream).Ĭommands that work in the pipeline fit into one of three categories: In Unix, it's common to pipe between commands to split up a sophisticated command over multiple steps.
Best intellectual property hornbook or nushell series#
These values can be piped through a series of steps, in a series of commands called a 'pipeline'.
Rather than thinking of files and data as raw streams of text, Nu looks at each input as something with structure.įor example, when you list the contents of a directory what you get back is a table of rows, where each row represents an item in that directory. Nu draws inspiration from projects like PowerShell, functional programming languages, and modern CLI tools. Please see our book for all of the Nushell documentation.
0 kommentar(er)
