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/whateveris giving me a headache. Actually just thinking aboutawkis 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
findbuiltin isn't a GNUfindrepacement. I think what you actually want islspiped intowhere:I do question the choice to alias a well-known program with a builtin that does something entirely different. You can also use
^findto 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 absolutely do what you want. GNU
findis 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.
You could also just alias
findback to^find. I don't use nushell as my daily driver for other reasons, and I agree with the comment above that it's a bit questionable for them to have a built-in with that name, but I don't understand why you'd even try out a new shell, let alone one that's radically different from POSIX-style shells, much less complain online about the shell you just tried, when you're already happy with the shell you're using and are not willing to adapt any habits or explore the configuration options to match your needs.I switched from GNU
findtofd2 years ago, unbeknownst to me at the time, this unlocked nu as a daily driver, which Iβve really enjoyed for the past year. I do fire up zsh semi-regularly when needed to escape some hairbrained corners. Scripting in nu is very nice thanks to the data manipulation and closure support. So nice to move from text manipulation to semantic structuring.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.
You can use both.
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 == filefindin 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.