This might make me a bit of a freak, but the one thing keeping me from trying out Fish for real is decent vim bindings. I know Fish has vim bindings, but I found the feature support pretty lackluster and the behavior of some keys like 'e' to be inaccurate.
I know some folks say that vim-style editing is overkill for a shell where you're often just submitting one-liners, but it saves so much time for me to be able to just jump right into the middle of a previous command and change one word without holding down arrow keys to get there.
Granted, it's been awhile since I looked into Fish's vim mode, so maybe it's improved. Last time I checked, it sounded like it just wasn't a priority, since Fish's selling point is the intelligent autocomplete and such.
If you are working on a complex, long command pipeline, in bash you can use Ctrl-x Ctrl-e to open your $EDITOR to edit the line as needed. The commands will be executed as soon as you save the file and exit.
I know some folks say that vim-style editing is overkill for a shell where you're often just submitting one-liners, but it saves so much time for me to be able to just jump right into the middle of a previous command and change one word without holding down arrow keys to get there.
Granted, it's been awhile since I looked into Fish's vim mode, so maybe it's improved. Last time I checked, it sounded like it just wasn't a priority, since Fish's selling point is the intelligent autocomplete and such.