OC by @phantomwise@lemmy.ml
I’ve been trying nushell and words fail me. It’s like it was made for actual humans to use! 🤯 🤯 🤯
It even repeats the column headers at the end of the table if the output takes more than your screen…
Trying to think of how to do the same thing with
awk
/grep
/sort
/whatever
is giving me a headache. Actually just thinking aboutawk
is giving me a headache. I think I might be allergic.I’m really curious, what’s your favorite shell? Have you tried other shells than your distro’s default one? Are you an awk wizard or do you run away very fast whenever it’s mentioned?
That’s basically how Powershell works.
*ducks*
This might be unpopular in Linux spaces but I consider Powershell for the most part well designed. I think its better suited to writing scripts than bash, but worse at being an interactive shell.
better suited to writing scripts than bash, but worse at being an interactive shell
And that’s totally fine. Different tools for use cases. 👌💪
A worse interactive shell than bash? No way, I find PowerShell closer to fish for interactive use.
It’s essentially an object oriented shell. It’s actually pretty good. But yeah, error outputs are a pain to read.
Yeah it was inspired by Powershell. But it also has syntax that isn’t completely awful.
what-do-you-mean-awful-syntax ?
Ha-Ha -exactly
Doesn’t look nearly as verbose either
Most bash fans I’ve known carve out an exception for powershell from their overall critique of windows. Personally, I think it’s not a fair comparison considering how god fucking awful everything else is in windows, but I do agree that it’s a decent shell.
Uh, this is dumb. I installed it and did a few things I would do on a normal basis. You’re telling me that this is not supported? It’s absolutely insane.
The commands are object-based instead of text based. The philosophy is built around chaining commands to filter data. I’m pretty sure the nushell command would be
ls ./ | where type == file
find
in nushell looks like it’s more for filtering the output of previous commands, not as a file search.not my jam, but I appreciate that. I used to do ‘find ./ | grep -i string’ forever. I’ve come to prefer the more robust usage of ‘find’ these days, -type, -iname, etc.
The “sort-by name” didn’t work as expected though…
Looking at the screenshot, I’d guess it sorted by the ASCII values of the characters, so processes with capitalized names come up first. Still not the ideal sorting, but at least makes some sense.
Explain?
It looks like powershell, but even nicer.
I’ve been using nushell for a year and while it is great mostly, and means you don’t need to use external tools like jq, the verbosity is tedious at times. I have a lot of aliases set, and I often use the caret escape hatch to run the traditional command if I just want a quick answer.
'Cause it was quarter past eleven
Like it was made for actual humans to use!
This is othering to the rest of us that just read manuals, understand how the tools work, and like them just fine.
Its fine to like nushell, no hate here, but you don’t have to dis what works (and has worked) for almost everyone else for so long.
What about: “wow I am really impressed with the QOL features in nushell!” Instead of “everyone who doesnt like this is not human”?
I genuinely can’t tell if you’re being sarcastic or not.