What I want to know:
1. In what specific ways is it better than zsh?
2. Is it absolutely, rock-solid stable?
11–20 of 155 posts
What I want to know:
1. In what specific ways is it better than zsh?
2. Is it absolutely, rock-solid stable?
Earlier quoted context omitted.
Why did they pick the exact same name?
Presumably because fish hasn't been updated since 2009 and they expect their fork to become the new standard version. http://ridiculousfish.com/shell/beta.html "Welcome to our fork of the fish shell, a command line shell like bash. Its working name is fishfish, but I hope eventually it will just be fish!"
Looks interesting. I expect my fingers will be even more confused than ever switching machines now (they've never learned that Alt-3 isn't # on linux or that middle-click isn't paste in Putty)
I use fish ( http://fishshell.com/ ), and it's amazing. However, they're missing the most important feature from their front page: Syntax highlighting! Valid executables are colored green, as you type. Invalid commands are red, as you type. Valid files are underlined, as you type. Like the carpenter who can feels the feedback of the grain of the wood through the handle of his plane can adjust his technique as he plan…
I stopped using fish a while ago, when it would crash whenever I opened a console session (so I couldn't do anything when X didn't start). I switched to zsh with fish emulation, but lately I realized I have a shell that takes much longer to start up and basically does everything fish does, and nothing more. If fishfish is more stable, I'll switch in a heartbeat.
The main reason for me to give it up is because I could not get it to work smoothly with rvm.
I've gotten quite used to zsh by now, and I have to say, I don't feel much for having another go at fish just to run into the same limitations again.
I use fish ( http://fishshell.com/ ), and it's amazing. However, they're missing the most important feature from their front page: Syntax highlighting! Valid executables are colored green, as you type. Invalid commands are red, as you type. Valid files are underlined, as you type. Like the carpenter who can feels the feedback of the grain of the wood through the handle of his plane can adjust his technique as he plan…
Why can't a better interactive history go hand in hand with something like "sudo !!"?
They need to update the slogan? "A command line shell for the 90s" doesn't really draw me in. What I want to know: 1. In what specific ways is it better than zsh? 2. Is it absolutely, rock-solid stable?
* autosuggestion
(this actually has a great amount of utility for me.
it complements tab-completion quite well!)
* optional web-based config
(great for quickly editing your config settings)
* speed improvements
(although I never suffered from much lag with fish
to begin with)
Overall I think the usability and utility of fish is greatly improved in this fork. Also it's worth pointing out that in terms of out-of-box functionality, some of fishfish features would be very hard to match. Things like autocompletion and simple history scrollback based one partial string matching set fish apart from the pack imo. So far, I'm quite impressed and I hope that more people adopt fishfish as the de facto replacement for fish.They need to update the slogan? "A command line shell for the 90s" doesn't really draw me in. What I want to know: 1. In what specific ways is it better than zsh? 2. Is it absolutely, rock-solid stable?
Earlier quoted context omitted.
Why did they pick the exact same name?
It's not called that yet: "Its working name is fishfish, but I hope eventually it will just be fish!" The ambition is quite reasonable as work on the fish shell itself has petered out, there was a recent dead cat bounce after a long fallow period, but it seems to be back to stasis there.
I'm quite happy living in the 80s.