Do we need a new shell or a few utilities that help produce structured output? For example, `ls | gen_structure | limit 50 | head 5`
Nushell: Introduction to a new kind of shell
61–70 of 252 posts
Re: Nushell: Introduction to a new kind of shell
#62Seems like a missed naming opportunity, it should've been "Nutshell" :D
Re: Nushell: Introduction to a new kind of shell
#63Earlier quoted context omitted.
Well, it is a good point, since nowadays PowerShell is also cross-platform, and seems to have more features than nushell does. Though the true reason is: I haven't really found the time to. Changing a shell is really stressful since you have to unlearn / relearn lots of things from muscle memory, and PowerShell's huge deviance from the rest of the POSIX-y world doesn't help. At least in nushell `rm -rf` works, the sa…
> PowerShell's huge deviance from the rest of the POSIX-y world doesn't help In PowerShell (on Windows), `rm` is an alias to `Remove-Item`[0]. Therefore, rm -r -fo An extra dash, extra space, and extra letter isn't too bad by my books. Furthermore, in scripts, aliases are discouraged by PSScriptAnalyzer[1]; IDEs (PowerShell ISE, VS Code PowerShell extension) also support code completion, so: Remove-Item -Recurse -For…
When PS has pushd, popd and dirs -v I’ll switch.
Re: Nushell: Introduction to a new kind of shell
#64Earlier quoted context omitted.
Anybody can say anything, that doesnt mean it should be taken seriously. "Done right" is probably that it is not done by MS and that it is developed in Rust. That ignores universe of other aspects.
Yes, let's go with your guess instead of trying to get an answer.
Indeed :) I have seen them all (answers).
Re: Nushell: Introduction to a new kind of shell
#65One issue I have with nushell is that on macOS they use the `Library/Application Support` path for the config instead of the `.config` making it awkward, their reason is that the former is the correct path of application data, while none of the other CLI apps I use do this, every other app just points to the `$HOME` dir or `.config` dir.
I used it for a while but I switched back to zsh, maybe in the future when it has a stable release I try it again, was too much hassle to update the config on almost each release. Also didn't worked well with some utils I use that has specific initialisation for each shell (i.e. rbenv).
Otherwise nushell seems to be a good contender for an alternative shell.
Re: Nushell: Introduction to a new kind of shell
#66Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.
So HN is not supposed to allow blog posts about projects but must always swap out for the project site itself? As someone who writes blog posts about projects, I hope not! It's not like this blog post is affiliate spam.
If the project site is better written and has the same content, yeah, I would prefer to see it.
But this is not the case here.
Re: Nushell: Introduction to a new kind of shell
#67Earlier quoted context omitted.
Why use this over PowerShell for example?
I am a C# programmer at heart, and I use powershell a good bit. I can honestly say I can never use powershell without my cheat sheets or my list of favorite commands (and especially the arguments to use). I looked at this and kinda get it and think I could do some things with it. I don't think it's as powerful and can _definitely_ say it won't be capable of the same automations we use. That said, the text parsing peo…
Do you use pwsh as your daily driver? I find that its commands are as easily memorable as any other shell.
That being said You should enable these:
Set-PSReadLineKeyHandler -Key Tab -Function MenuComplete
Set-PSReadLineOption -PredictionSource History
Re: Nushell: Introduction to a new kind of shell
#68> In a nutshell, nushell is non-POSIX shell, so most of your regular shells knowledge (zsh, bash, ksh, etc…) can't be applied on it, and using it feels like doing functional programming. Is there a reason some shells like fish (and now nushell) are non-POSIX? What is the benefit? I really like fish but I've kept away from it because it's non-POSIX and won't necessarily play well with years of POSIX scripts and knowle…
Is there a reason some shells like fish (and now nushell) are non-POSIX?
Some things are different than other things. It's the same reason that not all desserts are pie, and not all automobiles are trucks.
Re: Nushell: Introduction to a new kind of shell
#69One issue I have with nushell is that on macOS they use the `Library/Application Support` path for the config instead of the `.config` making it awkward, their reason is that the former is the correct path of application data, while none of the other CLI apps I use do this, every other app just points to the `$HOME` dir or `.config` dir. I used it for a while but I switched back to zsh, maybe in the future when it ha…
surely something as basic as the location of the config folder can somehow be changed to a custom path, right?
Re: Nushell: Introduction to a new kind of shell
#70Earlier quoted context omitted.
WSL is great but it’s basically a convenient VM. It’s no longer windows, as far as I’m concerned.
It's literally a subsystem. It's integrated in many ways you would not use to describe a "VM". I don't understand the aversion nor the confusion.
Here’s an example: if I build a Python app with PyInsyaller (which can’t cross-compile), and if I want a Windows executable, I have to build on Windows, not WSL, which defeats the whole purpose of “bash on Windows” because now at best I have to use Cygwin or Powershell or something and deal with a completely different environment.