站内导读
定位:Nushell 是一款新型 shell,由开源社区维护,已达到可日常使用的水平,适合在终端里替代或补充传统 shell 处理命令与文件。
核心能力
- 以管道为基本设计,README 把 Pipelines 列为理念首项,命令之间的连接方式与传统 shell 不同。
- 打开文件单独成节,说明 Nu 读取文件、把内容接入管道的处理方式,与只输出文本的 shell 有区别。
- 提供插件机制,Plugins 与 Pipelines、Opening files 并列,用于扩展内置命令之外的能力。
- 通过 brew、winget 等多家包管理器分发,GitHub Actions 中可用 setup-nu 安装,平台支持范围另有文档说明。
适用人群:长期在终端里工作的开发者与运维人员,需要 Linux、macOS 或 Windows 环境,能读英文文档,并接受命令行为随版本调整。
位置づけ:Nushell はオープンソースコミュニティが保守する新しいタイプのシェルで、日常利用に耐える水準に達している。ターミナルで従来のシェルを置き換えたり補ったりして、コマンドやファイルを扱う用途に向く。
主な機能
- パイプラインを基本設計とし、README でも Pipelines が理念の筆頭に挙げられている。コマンド同士のつなぎ方は従来のシェルと異なる。
- ファイルを開く操作が独立した節になっており、Nu がファイルを読み取り、その内容をパイプラインへ流す方法を説明している。テキストだけを出力するシェルとは異なる点。
- プラグイン機構があり、Pipelines やファイル処理と並列に置かれ、組み込みコマンド以外の能力を拡張できる。
- brew、winget など複数のパッケージマネージャで配布され、GitHub Actions では setup-nu で導入できる。対応プラットフォームは別途ドキュメントに記載。
向いている人:ターミナルで長時間作業する開発者や運用担当者。Linux、macOS、Windows 環境が必要で、英語ドキュメントが読め、コマンドの挙動がバージョンで変わることを受け入れられる人。
정의: Nushell은 오픈소스 커뮤니티가 유지보수하는 새로운 유형의 셸로, 일상적으로 쓸 수 있는 수준에 도달했다. 터미널에서 기존 셸을 대체하거나 보완하며 명령과 파일을 다루는 데 적합하다.
핵심 기능
- 파이프라인을 기본 설계로 삼아 README에서도 Pipelines가 이념의 첫 항목으로 꼽힌다. 명령끼리 연결하는 방식이 기존 셸과 다르다.
- 파일 열기가 별도 절로 다뤄지며, Nu가 파일을 읽어 그 내용을 파이프라인에 흘려보내는 방식을 설명한다. 텍스트만 출력하는 셸과의 차이점이다.
- 플러그인 메커니즘이 Pipelines, 파일 처리와 나란히 자리해 기본 명령 너머의 기능을 확장할 수 있다.
- brew, winget 등 여러 패키지 관리자로 배포되며 GitHub Actions에서는 setup-nu로 설치할 수 있다. 지원 플랫폼은 별도 문서에 설명되어 있다.
대상: 터미널에서 오래 작업하는 개발자와 운영 담당자. Linux, macOS, Windows 환경이 필요하고 영어 문서를 읽을 수 있으며, 명령 동작이 버전에 따라 달라지는 것을 받아들일 수 있어야 한다.
What it is: Nushell is a new type of shell maintained by an open-source community; it has reached minimum-viable-product quality and is already used as a daily driver by many people.
Key capabilities
- Pipelines come first in the philosophy section: commands are connected in a way that differs from a text-only shell.
- Opening files gets its own section, covering how Nu reads a file and feeds its contents into a pipeline.
- A plugin mechanism sits alongside pipelines and file handling, extending what built-in commands can do.
- Packages ship through brew, winget and many other package managers; setup-nu installs Nu inside GitHub Actions.
README · 详细文档
来源 · 查看原文
Nushell
A new type of shell.
Example of nushell
Table of Contents
- Status
- Learning About Nu
- Installation
- Configuration
- Philosophy
- Pipelines - Opening files - Plugins
- Goals
- Officially Supported By
- Contributing
- License
Status
This project has reached a minimum-viable-product level of quality. Many people use it as their daily driver, but it may be unstable for some commands. Nu's design is subject to change as it matures.
Learning About Nu
The Nushell book is the primary source of Nushell documentation. You can find a full list of Nu commands in the book, and we have many examples of using Nu in our cookbook.
We're also active on Discord; come and chat with us!
Installation
To quickly install Nu:
# Linux and macOS
brew install nushell
# Windows
winget install nushell
To use Nu in GitHub Action, check setup-nu for more detail.
Detailed installation instructions can be found in the installation chapter of the book. Nu is available via many package managers:
For details about which platforms the Nushell team actively supports, see our platform support policy.
Configuration
The default configurations can be found at sample_config which are the configuration files one gets when they start up Nushell for the first time.
It sets all of the default configuration to run Nushell. From here one can then customize this file for their specific needs.
To see where config.nu is located on your system simply type this command.
$nu.config-path
Please see our book for all of the Nushell documentation.
Philosophy
Nu draws inspiration from projects like PowerShell, functional programming languages, and modern CLI tools. Rather than thinking of files and data as raw streams of text, Nu looks at each input as something with structure. For 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. These values can be piped through a series of steps, in a series of commands called a 'pipeline'.
Pipelines
In Unix, it's common to pipe between commands to split up a sophisticated command over multiple steps. Nu takes this a step further and builds heavily on the idea of pipelines. As in the Unix philosophy, Nu allows commands to output to stdout and read from stdin. Additionally, commands can output structured data (you can think of this as a third kind of stream). Commands that work in the pipeline fit into one of three categories:
- Commands that produce a stream (e.g.,
ls) - Commands that filter a stream (e.g.,
where type == "dir") - Commands that consume the output of the pipeline (e.g.,
table)
Commands are separated by the pipe symbol (|) to denote a pipeline flowing left to right.
ls | where type == "dir" | table
# => ╭────┬──────────┬──────┬─────────┬───────────────╮
# => │ # │ name │ type │ size │ modified │
# => ├────┼──────────┼──────┼─────────┼───────────────┤
# => │ 0 │ .cargo │ dir │ 0 B │ 9 minutes ago │
# => │ 1 │ assets │ dir │ 0 B │ 2 weeks ago │
# => │ 2 │ crates │ dir │ 4.0 KiB │ 2 weeks ago │
# => │ 3 │ docker │ dir │ 0 B │ 2 weeks ago │
# => │ 4 │ docs │ dir │ 0 B │ 2 weeks ago │
# => │ 5 │ images │ dir │ 0 B │ 2 weeks ago │
# => │ 6 │ pkg_mgrs │ dir │ 0 B │ 2 weeks ago │
# => │ 7 │ samples │ dir │ 0 B │ 2 weeks ago │
# => │ 8 │ src │ dir │ 4.0 KiB │ 2 weeks ago │
# => │ 9 │ target │ dir │ 0 B │ a day ago │
# => │ 10 │ tests │ dir │ 4.0 KiB │ 2 weeks ago │
# => │ 11 │ wix │ dir │ 0 B │ 2 weeks ago │
# => ╰────┴──────────┴──────┴─────────┴───────────────╯
Because most of the time you'll want to see the output of a pipeline, table is assumed. We could have also written the above:
ls | where type == "dir"
Being able to use the same commands and compose them differently is an important philosophy in Nu. For example, we could use the built-in ps command to get a list of the running processes, using the same where as above.
ps | where cpu > 0
# => ╭───┬───────┬──────┬───────────┬──────┬─────────┬───────┬────────────┬──────────╮
# => │ # │ pid │ ppid │ name │ user │ status │ cpu │ cpu_time │ mem │
# => ├───┼───────┼──────┼───────────┼──────┼─────────┼───────┼────────────┼──────────┤
# => │ 0 │ 2240 │ 9872 │ Slack.exe │ dev │ Running │ 16.40 │ 1min 12sec │ 178.3 MB │
# => │ 1 │ 16948 │ 9872 │ Slack.exe │ dev │ Running │ 16.32 │ 48sec │ 205.0 MB │
# => │ 2 │ 17700 │ 4632 │ nu.exe │ dev │ Running │ 3.77 │ 2sec │ 26.1 MB │
# => ╰───┴───────┴──────┴───────────┴──────┴─────────┴───────┴────────────┴──────────╯
Opening files
Nu can load file and URL contents as raw text or structured data (if it recognizes the format). For example, you can load a .toml file as structured data and explore it:
open Cargo.toml
# => ╭──────────────────┬────────────────────╮
# => │ bin │ [table 1 row] │
# => │ dependencies │ {record 25 fields} │
# => │ dev-dependencies │ {record 8 fields} │
# => │ features │ {record 10 fields} │
# => │ package │ {record 13 fields} │
# => │ patch │ {record 1 field} │
# => │ profile │ {record 3 fields} │
# => │ target │ {record 3 fields} │
# => │ workspace │ {record 1 field} │
# => ╰──────────────────┴────────────────────╯
We can pipe this into a command that gets the contents of one of the columns:
open Cargo.toml | get package
# => ╭───────────────┬────────────────────────────────────╮
# => │ authors │ [list 1 item] │
# => │ default-run │ nu │
# => │ description │ A new type of shell │
# => │ documentation │ https://www.nushell.sh/book/ │
# => │ edition │ 2018 │
# => │ exclude │ [list 1 item] │
# => │ homepage │ https://www.nushell.sh │
# => │ license │ MIT │
# => │ metadata │ {record 1 field} │
# => │ name │ nu │
# => │ repository │ https://github.com/nushell/nushell │
# => │ rust-version │ 1.60 │
# => │ version │ 0.72.0 │
# => ╰───────────────┴────────────────────────────────────╯
And if needed we can drill down further:
open Cargo.toml | get package.version
# => 0.72.0
Plugins
Nu supports plugins that offer additional functionality to the shell and follow the same structured data model that built-in commands use. There are a few examples in the crates/nu_plugins_* directories.
Plugins are binaries that are available in your path and follow a nu_plugin_* naming convention. 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. 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. If the plugin is a sink, it is given the full vector of final data and is given free reign over stdin/stdout to use as it pleases.
The awesome-nu repo lists a variety of nu-plugins while the showcase repo shows off informative blog posts that have been written about Nushell along with videos that highlight technical topics that have been presented.
Goals
Nu adheres closely to a set of goals that make up its design philosophy. As features are added, they are checked against these goals.
- First and foremost, Nu is cross-platform. Commands and techniques should work across platforms and Nu has first-class support for Windows, macOS, and Linux.
- Nu ensures compatibility with existing platform-specific executables.
- Nu's workflow and tools should have the usability expected of modern software in 2022 (and beyond).
- Nu views data as either structured or unstructured. It is a structured shell like PowerShell.
- Finally, Nu views data functionally. Rather than using mutation, pipelines act as a means to load, change, and save data without mutable state.
Officially Supported By
Please submit an issue or PR to be added to this list.
Contributing
See Contributing for details. Thanks to all the people who already contributed!
License
The project is made available under the MIT license. See the LICENSE file for more information.