121–130 of 146 posts
Now I work at Google where there are tons of shared bash commands and scripts. It's so easy to simply copy/paste something that works into your shell instead of futzing around with compatibility differences.
It'd be neat to work at a place where everyone used fish but I've never experienced that.
Earlier quoted context omitted.
Thank you! I've been using Nushell for a couple of weeks and at this point I don't see myself going back. Modern configuration. Great interactive usage (structured data, mostly!). I thought I'd like it, but more so than expected so far. The one shortcoming I've encountered so far is that some built-in functions seem to buffer all their input before producing any output, meaning I can't e.g. tail + filter logs. A fair…
Ahh, streaming. This is an area I've been working on; there are still lots of places where we collect data when we should stream it instead. In general, if you think "that should be able to stream" but it doesn't, that's probably a bug and worth filing an issue. I can reproduce your issue, I suspect that `filter` is collecting its input when it shouldn't. It's not totally clear why from looking at the code. If you ca…
https://github.com/nushell/nushell/issues/8016
I couldn't apply labels myself, I don't think.
I was very happy with zsh and fish when I was at small companies or grad school. Now I work at Google where there are tons of shared bash commands and scripts. It's so easy to simply copy/paste something that works into your shell instead of futzing around with compatibility differences. It'd be neat to work at a place where everyone used fish but I've never experienced that.
Earlier quoted context omitted.
Most things in fish can be achieved with customization and configuration in other shells, like zsh or bash. The point of fish is a sane set of defaults that doesn't require customization and is good enough.
If you want zsh that acts like fish, try "fizsh".
Earlier quoted context omitted.
nushell has a similar philosophy to PowerShell but without the strange command names. PowerShell is probably tied too deeply to Windows and .NET to be suitable as a Linux shell
PowerShell has strange command names? Compared to what? grep, sed, awk, and a bunch of two letter abbreviations from the before-times?
I was very happy with zsh and fish when I was at small companies or grad school. Now I work at Google where there are tons of shared bash commands and scripts. It's so easy to simply copy/paste something that works into your shell instead of futzing around with compatibility differences. It'd be neat to work at a place where everyone used fish but I've never experienced that.
It's easy, you can just add bash to the beginning of the code and you can run the same script there.
I really like it despite its quirks. I love the implicit $in variable. I find the library easy to understand. I'm only using it interactively so if I have to restart my terminal every once in a while I'm not bothered by it. I trust that those sorts of things will get straightened out --- the git repository is very active.
I saw the maintainers in this thread, so shout out for your good work.
Earlier quoted context omitted.
If you want zsh that acts like fish, try "fizsh".
That is so cool, people really think of everything don't they?
I use `fish` as my main shell. It's closer to POSIX than eshell or oil, but it's definitely not POSIX. Personally, the main thing I like about it is that I can't copy paste bash commands. It forces me to read and understand and then convert. It also has some quality of life stuff I really like. I think next time I'm just going to go back to ZSH though as I feel I have learnt enough from the experience of using it tha…
When there's something called deadline that's no longer feasible