Nsh: A fish/bash-like Posix shell in Rust

Looks like the goal of this project is to be a replacement for bash with improved interactivity. That seems reasonable, compared to what you can do with zsh or fish bash is far behind concerning interactivity.<p>While I personally think shells that abandon POSIX&#x2F;bash compliance are much more interesting as those can implement a sane scripting language, sticking with bash but improving interactivity is probably going to make more users happy as bash is so ubiquitous.

This project looks very young. It might evolve into a contender but even the document on Bash compatibility just says &quot;TODO&quot; and frankly Bash compatibility is going to be a multi-year project on its own.<p>For anyone after an upgrade path from Bash&#x2F;Zsh then Oil shell is a lot more mature: <a href="https:&#x2F;&#x2F;www.oilshell.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.oilshell.org&#x2F;</a>

&gt; Fish is really neat but I prefer old-fashioned, traditional, and ergonomic shell syntax.<p>What does this really mean? Especially the ergonomic part?

I have used fish for years, it is just painful to watch how other people work with old fashion shells.<p>I applaud this project for bringing fish goodness to more people, although I don’t quite get why people cannot just learn fish. Fish is very simple. There is not that much to learn.<p>Maybe it matters if your write a lot of shell scripts but for anything complicated I use Julia, Python, Go or some other more proper language.<p>To me shells are mainly for interactive work and really simple scripts without control flow, beyond perhaps a for loop.

&gt; I don&#x27;t need customizability<p>Configuration isn&#x27;t for you. It&#x27;s for other people. Configuration is the part of a program that performs the function of making it useful for more than one person. It is the necessary glue that brings together many developers and many users into one project.

The name sounds very similar to Nushell[1], also written in Rust, but more mature and recognizable<p>1: <a href="https:&#x2F;&#x2F;www.nushell.sh&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.nushell.sh&#x2F;</a>

Very cool. I really love fish but sometimes find it very annoying to translate random posix snippets from the web.

There is also <a href="https:&#x2F;&#x2F;github.com&#x2F;nixpulvis&#x2F;oursh" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;nixpulvis&#x2F;oursh</a> which wants to be POSIX compatible with its own extensions. Actually I would prefer if a new shell focuses on bash compatibility.<p>If features are integrated, then I would probably want to have something about error handling because it is difficult to get right in bash even with shellcheck¹ plus shellharden², and gets just worse when things run in parallel.<p>¹ <a href="https:&#x2F;&#x2F;www.shellcheck.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.shellcheck.net&#x2F;</a><p>² <a href="https:&#x2F;&#x2F;github.com&#x2F;anordal&#x2F;shellharden" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anordal&#x2F;shellharden</a>

Just a heads up: name collision with the default shell on (now Apache) Nuttx.<p><a href="http:&#x2F;&#x2F;nuttx.incubator.apache.org&#x2F;docs&#x2F;latest&#x2F;applications&#x2F;nsh&#x2F;index.html" rel="nofollow">http:&#x2F;&#x2F;nuttx.incubator.apache.org&#x2F;docs&#x2F;latest&#x2F;applications&#x2F;n...</a>

Will this support native windows? The main reason I have switched to nushell is because it is cross platform

Nice! I see nsh uses threads internally. Any plans on how to handle the fork-thread interaction?