- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
OC by @[email protected]
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?
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.
Nu’s
find
builtin isn’t a GNUfind
repacement. I think what you actually want isls
piped intowhere
:I do question the choice to alias a well-known program with a builtin that does something entirely different. You can also use
^find
to avoid calling the builtin. I would’ve expected\find
(bash-like) orcommand find
(fish-like) to work as well, but alas…I don’t think that’s what I’d actually want, no. I want GNU find functionality for this to be a viable shell replacement. It’s… neat, but it’s no daily driver.
back to /bin/zsh for me!
You can use both.
you can absolutely do what you want. GNU
find
is external and since it conflicts with a builtin can be aliased or referenced like^find
.the syntax is new for sure, and it’s not for everyone.
been daily driving for over a year
I prefer flow to futz. Thanks for the info. Glad it’s working for you. I’m staying with what works well for me.
They kinda have to replace some coreutils like find from scratch to be compatible with their philosophy of piping data tables instead of text. It’s super cool and ends up being really powerful but yeah it’s a whole new ecosystem which makes it pretty much impossible to be a drop-in shell replacement.
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.https://www.nushell.sh/commands/docs/ls.html
https://www.nushell.sh/commands/docs/find.html
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.