Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It seems this "shell" is not designed to execute commands by default? "Native Shell Commands" section[0] actually says:
> Nu allows you to access native shell programs by escaping the program name with ^.
> sc is a Windows CMD program that is used for communicating with the Service Control Manager
I'll argue that if you cannot enter the name of executable on the line directly and have it executed, it is not an actual "shell", but just some sort of interactive-oriented language.
Also author calling sc.exe "an Windows CMD program" makes me suspect that author is not very familiar with low-level shell concepts such as "terminal", "console", "PATH" and so on. A random sample of source code, which always hardcodes "sh" for shell files (! no bash for you, buddy !) seems to support this [1].
[0] https://www.nushell.sh/cookbook/native_shell_programs.html
[1] https://github.com/nushell/nushell/blob/565be6aaefc60be15426...
I’m using this shell daily, because it also works very well on Windows out of the box, without installing Cygwin or MSYS.
The other option for Windows users for a sane, usable shell (cmd is frankly put, shit), is busybox-w32 (https://frippery.org/busybox). But then you miss out on any of the fancy autocompletion or syntax highlighting (which is what I’m primarily using nu-shell for, I haven’t even tried their structural data stuff yet and it’s already good as a Windows shell.)