Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

Post by [deleted] » Thu, Feb 09, 2023, 1:38 PM UTC

JonChesterfield wrote: post #26

anonyfox wrote: post #18

I am still kinda bitter about mac os replacing the default bash with zsh. I gained nothing from that unwanted update, but got compatibility pains suddenly. Is something is more complicated than a one-liner, use a real programming language instead, with proper building blocks, tooling and documentation. Use something like Go to crosscompile if you don't want to depend on something on the host machine. In my experience…

I've watched a one line bash pipeline turn into a thousand line python program over the course of about a week. It didn't need new functionality, it was just not proper engineering to leave it in bash. We never did agree on whether that was right or not. It was something involving digging information out of elf binaries where the python libs were much more verbose than the flags passed to readelf (maybe objdump, it w…

Post by davelondon » Thu, Feb 09, 2023, 1:52 PM UTC

pringk02 wrote: post #17

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…

Post by manimino » Thu, Feb 09, 2023, 2:17 PM UTC

cube2222 wrote: post #45

robochat wrote: post #25

Earlier quoted context omitted.

You can easily get bash to do that by adding these lines to your .inputrc file. "\e[A": history-search-backward "\e[B": history-search-forward "\e[C": forward-char "\e[D": backward-char

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.

Post by arp242 » Thu, Feb 09, 2023, 2:23 PM UTC

maxloh wrote: post #51

Nushell is great for simple tasks. i.e. ls **/data.json | each {|it| mv $it.name $"(dirname $it.name)/data.yml" } Will be much more complex in bash find -name "data.json" | xargs -i bash -c "mv \"{}\" \"\$(dirname '{}')/data.yml\"" Note the escaped quotes and dollar signs in bash. It is really difficult to get them right. In Nutshell we are actually using "functions" (supported syntax-wise) to do the job, so it will…

  for f in **/data.json; mv $f $f:r.yaml

  for f in **/data.json; do mv $f ${f%.json}.yaml; done

Post by oblio » Thu, Feb 09, 2023, 2:32 PM UTC

zioroboco wrote: post #70

I've been using nushell for the past year, and I love it. For a while I kept bash as my login shell and had nu as my default command in tmux. This had the advantage of allowing a bunch of environment setup to run in bash and get inherited, which allowed my overall setup to be more vanilla (and also nushell doesn't have any kind of job control, so something like tmux is probably a must). About two months ago I promote…