Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fish shell

fishshell.com

Post reply on HN
Print view View original

131–140 of 188 posts

Re: Fish shell

#131

Post by cbd1984 »

ridiculous_fish wrote: post #100

Hey, I'm the lead dev of the fish shell. There's some great discussion in this thread! For those who are interested, the fish shell is about to release version 2.2, a very significant release that wraps up eighteen months of development. You can try the beta now: http://fishshell.com/beta/ A sampling of new features: - vi mode (yay!) - Abbreviations, fish's take on aliases. They expand as you type them. - A new "inli…

If they can't write a page without useless frills, they can't write a shell without useless frills.

Useless frills are buggy and slow.

Re: Fish shell

#132

Post by mintplant »

nkouevda wrote: post #117
eridius wrote: post #57

Earlier quoted context omitted.

> vi-mode, obviously As you said at the end, Fish does have this. I don't know if it's full-featured enough for you though. > Control+R. It is annoying to have to guess how much you must type before hitting the up arrow, instead of having it dynamically displayed When you start typing a command-line in Fish that matches a previously-typed command, it automatically shows the rest of the line as an available completion…

> When you start typing a command-line in Fish that matches a previously-typed command, it automatically shows the rest of the line as an available completion, and pressing ^F or the right arrow will complete it for you. ^R is more powerful, though; it matches at any point in previous commands, not just at the beginning. > The lack of this functionality actually really kills my ability to use any other shell. You can…

> ^R is more powerful, though; it matches at any point in previous commands, not just at the beginning.

That's how it works in Fish as well.

    user@system ~> echo wow
    wow
    user@system ~> echo something
    something
    user@system ~> wow█
...press the up arrow and the current line becomes...

    user@system ~> echo wow█

Re: Fish shell

#133

Post by bojo »

ridiculous_fish wrote: post #100

Hey, I'm the lead dev of the fish shell. There's some great discussion in this thread! For those who are interested, the fish shell is about to release version 2.2, a very significant release that wraps up eighteen months of development. You can try the beta now: http://fishshell.com/beta/ A sampling of new features: - vi mode (yay!) - Abbreviations, fish's take on aliases. They expand as you type them. - A new "inli…

Seriously looking forward to this release! Been an avid user for over a year now and absolutely love this shell. Still get the odd strange look when I mention what I use though :)

Re: Fish shell

#134

Post by humility »

ridiculous_fish wrote: post #100

Hey, I'm the lead dev of the fish shell. There's some great discussion in this thread! For those who are interested, the fish shell is about to release version 2.2, a very significant release that wraps up eighteen months of development. You can try the beta now: http://fishshell.com/beta/ A sampling of new features: - vi mode (yay!) - Abbreviations, fish's take on aliases. They expand as you type them. - A new "inli…

Great work!!

Re: Fish shell

#136

Post by BorisMelnik »

I've been a Linux command line (bash) user for 20+ years now and I must say, I would really consider switching to this. I haven't even started to dig into the features yet, but the filename and parameter completion alone is enough to stop me from pulling my hair out.

Filenames are getting very long w/ so many special characters, this is great. I also like the idea of having a web based config. I really won't miss wrestling with bashrc and bashconfig in vi. Definitely will try this.

Re: Fish shell

#137

Post by ridiculous_fish »

Karunamon wrote: post #114
tomphoolery wrote: post #76

Earlier quoted context omitted.

OMZ got painfully slow for me when I used it with a lot of plugins and it was iterating over a lot of different file paths. It seems like ZSH has an issue when you're loading a mass amount of files...or maybe it's just the way OMZ is loading them?

Are you on a mac by chance? I ran into a really weird problem on OSX, still happens as of the latest Yosemite beta, where if you have a lot of system logs laying around, the shell takes an inordinately long time to start (10+ seconds) and do autocompletes. If you clear out your logfiles by trashing /private/var/log/asl/*.asl, there's a pretty decent speedup.

A permanent fix for this is to create a file called .hushlogin in your home directory. I do it on all my machines.

Re: Fish shell

#138

Post by Matumio »

mintplant wrote: post #132
nkouevda wrote: post #117

Earlier quoted context omitted.

> When you start typing a command-line in Fish that matches a previously-typed command, it automatically shows the rest of the line as an available completion, and pressing ^F or the right arrow will complete it for you. ^R is more powerful, though; it matches at any point in previous commands, not just at the beginning. > The lack of this functionality actually really kills my ability to use any other shell. You can…

> ^R is more powerful, though; it matches at any point in previous commands, not just at the beginning. That's how it works in Fish as well. user@system ~> echo wow wow user@system ~> echo something something user@system ~> wow█ ...press the up arrow and the current line becomes... user@system ~> echo wow█

In bash, you hit Ctrl-R on the empty prompt and type "w":

    (reverse-i-search)`w': echo wow
Hit return to execute, or any motion keys to start editing. It was the first thing I missed in Fish.

Re: Fish shell

#139

Post by girvo »

nkouevda wrote: post #117
eridius wrote: post #57

Earlier quoted context omitted.

> vi-mode, obviously As you said at the end, Fish does have this. I don't know if it's full-featured enough for you though. > Control+R. It is annoying to have to guess how much you must type before hitting the up arrow, instead of having it dynamically displayed When you start typing a command-line in Fish that matches a previously-typed command, it automatically shows the rest of the line as an available completion…

> When you start typing a command-line in Fish that matches a previously-typed command, it automatically shows the rest of the line as an available completion, and pressing ^F or the right arrow will complete it for you. ^R is more powerful, though; it matches at any point in previous commands, not just at the beginning. > The lack of this functionality actually really kills my ability to use any other shell. You can…

> kills my ability to use any other shell

zsh definitely has this command, which I absolutely adore to be honest. ^R is one of my favourite features of the shell in general.

Re: Fish shell

#140

Post by codychan »

codychan wrote: post #116
ridiculous_fish wrote: post #100

Hey, I'm the lead dev of the fish shell. There's some great discussion in this thread! For those who are interested, the fish shell is about to release version 2.2, a very significant release that wraps up eighteen months of development. You can try the beta now: http://fishshell.com/beta/ A sampling of new features: - vi mode (yay!) - Abbreviations, fish's take on aliases. They expand as you type them. - A new "inli…

BTW, you should mention https://github.com/fish-shell/fish-shell/wiki/Nightly-builds after "You can try the beta now", because I cannot get beta at http://fishshell.com/beta/

Unless you want to install it from the tar.gz file
Post reply on HN