Live data from Hacker News

Fish shell 3.0

github.com

31–40 of 227 posts

Re: Fish shell 3.0

#31
post #29
post #26

Earlier quoted context omitted.

How do you go to the nth item of the directory stack? Even bash lets you do this: $ dirs -v 0 ~/baz 1 ~ 2 ~/bar 3 ~/foo 4 ~/spam Then "pushd +3" will take you to ~/foo. This hardly seems "opaque".

That's included, just the `~2` shortcut thing isn't.

Which is included? I couldn't find anything like "dirs -v" in the fish manual. Without that, "pushd +N" isn't very useful.

Re: Fish shell 3.0

#32
post #31
post #29

Earlier quoted context omitted.

That's included, just the `~2` shortcut thing isn't.

Which is included? I couldn't find anything like "dirs -v" in the fish manual. Without that, "pushd +N" isn't very useful.

[deleted]

Re: Fish shell 3.0

#35
post #14
post #8

Earlier quoted context omitted.

Coming from ZSH, Fish is a shell that just worked out of the box for me. It did everything ZSH did but I didn't have to touch a single configuration file to make it work. With ZSH I was forced to find all the options I wanted enabled and tuned or had to resort oh-my-zsh or templates from others to get all the good stuff. Managing dotfiles across workstations and servers. With Fish about the only thing I do after inst…

”Fish is a shell that just worked out of the box for me” Same here. Fish’s configuration defaults are very well thought out and incredibly smooth. My config.fish is only nine lines.

And when you do want to configure it, you can choose to use either config.fish or the web-based configuration tool. The web tool is very nicely thought out and lets you preview themes and such before you use them.

Re: Fish shell 3.0

#36

>? as a glob (wildcard) is deprecated and will be removed in the future ( https://github.com/fish-shell/fish-shell/issues/4520 ) This surprised me, but maybe it's for the best. It got in my way more often than I used it. I'll still miss it.

It makes pasting unescaped data (read: URLs) and writing raw regexes easier (esp because ^ is no longer a reserved character as well).

Re: Fish shell 3.0

#37
I've been happily using fish for maybe two years now, just as a default shell and not doing anything fancy. Out of the box it is great.

I'm not sure how to feel about only now learning its indexes start at a [1] though (╯°□°)╯︵ ┻━┻

Love it otherwise.

Re: Fish shell 3.0

#38
I made fish my default shell for around a month, and I really liked the smart suggestions of what command I was going for when I started typing. But the "vi" mode had enough incompatibilities that it really irritated me, it was extremely incomplete. Discussions of it with devs went nowhere. Plus, there were incompatibilities in the language that I could never bring myself to commit to memory; I might have if the vi mode were better but as it was I didn't want to get any further invested in it than I was.

In the end I switched back to zsh and enabled "zsh-autosuggestions", which gave me the thing I loved most about fish, without any of the parts that I didn't. There's also some other extensions I'd like to try that enhance history like "McFly" ( https://github.com/cantino/mcfly ), based on this previous zsh-histdb discussion: https://news.ycombinator.com/item?id=15041772

Re: Fish shell 3.0

#40

Apart from the other good stuff in this release, I think this will make a lot of things much easier: fish now supports && (like and), || (like or), and ! (like not), for better migration from POSIX-compliant shells

Though I've really grown toward the 'everything as a function' pattern that Fish is trying to do, this is definitely a step back in the right direction. I might even wish for `$()` to be supported as well to allow even better copy pastable oneliners from Bash.

I thought it was to be included in 3.0, there's certainly an issue on it.
Post reply on HN