That's basically how Powershell works.
*ducks*
That's basically how Powershell works.
*ducks*
Nushell is so cool! Iβm happy itβs still progressing; I was worried it would die out because itβs such a leap from existing shells that they kinda need to develop an ecosystem from scratch. Piping actual data tables between commands is brilliant. Iβve tried using it as a daily driver but it takes some work to convert existing dot files and scripts. I might try it again.
Neat. After reading the docs for a bit, it seemed like the sort of shell that would be made by Rust programmers. What do you know, that guess is correct.
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 GNU find repacement. I think what you actually want is ls piped into where:
ls **/* | where type == file
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) or command 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 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.
You could also just alias find back 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 find to fd 2 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.
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.
Remember to subscribe or post in https://programming.dev/c/nushell or other communities on the fediverse!
The "sort-by name" didn't work as expected though...
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.
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 love nu, but I know it's a lot for people. I can't go back to bash anymore.
top 33 comments