4 ms·

I gave fish a serious try last year, and really loved the command-line completion, but the vi mode editing was a deal-breaker. It's minimally usable, in partic

I gave fish a serious try last year, and really loved the command-line completion, but the vi mode editing was a deal-breaker. It's minimally usable, in particular it doesn't support command combinations like dt/ ct/ ; d0 etc... In the end I found a history completion plugin for zsh that worked as well as fish, and ended up going back to zsh. The vi mode issue seems pretty hard to resolve, like have to completely reimplement the editing hard. You can, as an alternative, drop to a real editor if you need a real editor for the command. Here's the issue related to it: https://github.com/fish-shell/fish-shell/issues/4019 https://github.com/fish-shell/fish-shell/issues/4019 It's very interesting, but I'm pretty dead set on vi history editing, so it wasn't for me. (Edit to update the commands it has issues with)

Gaelan 6y ago
I just tried dw, cw, f/, and df/, and they all worked just fine.
- linsomniac 6y ago
  I was misremembering, it was the combination with motion commands: dt/ ct/ ; d0 -- if these work now you probably want to provide feedback on the issue I mentioned above, because it's still marked as open.
  - Gaelan 6y ago
    dt/ cw and d0 work, but ct/ doesn't. Seems like maybe they've hardcoded certain command-motion combinations, but not actually done it "properly." FWIW, it acts enough like vi that I never noticed until today.
zanchey 6y ago
To reprise a previous comment, I think vi mode suffers because it's a relatively niche feature - none of the current committers use it as far as I know, and pull requests to improve it are relatively infrequent. 1.8% of the pull requests into the (not yet released) 3.2.0 are for Vi mode, which is a slight increase on previous milestones, and includes support for dh, dl, c0, cf, ct, cF, cT, ch, cl, y0, tilde, ci', ci", yi', yi", di' and di". I don't think it helps that it's this huge target area which (the small number of?) users use a slightly different 10% of, and it can be quite complex to integrate new features into existing editor state.
- linsomniac 6y ago
  Sure, understandable and reasonable. Just wanted to mention it for others that may care. Fish has some great stuff in there. But, in my case, 30 years of vi muscle memory was hard to blunt.

Gaelan 6y ago

I just tried dw, cw, f/, and df/, and they all worked just fine.

linsomniac 6y ago
I was misremembering, it was the combination with motion commands: dt/ ct/ ; d0 -- if these work now you probably want to provide feedback on the issue I mentioned above, because it's still marked as open.
- Gaelan 6y ago
  dt/ cw and d0 work, but ct/ doesn't. Seems like maybe they've hardcoded certain command-motion combinations, but not actually done it "properly." FWIW, it acts enough like vi that I never noticed until today.

zanchey 6y ago

To reprise a previous comment, I think vi mode suffers because it's a relatively niche feature - none of the current committers use it as far as I know, and pull requests to improve it are relatively infrequent. 1.8% of the pull requests into the (not yet released) 3.2.0 are for Vi mode, which is a slight increase on previous milestones, and includes support for dh, dl, c0, cf, ct, cF, cT, ch, cl, y0, tilde, ci', ci", yi', yi", di' and di". I don't think it helps that it's this huge target area which (the small number of?) users use a slightly different 10% of, and it can be quite complex to integrate new features into existing editor state.

linsomniac 6y ago
Sure, understandable and reasonable. Just wanted to mention it for others that may care. Fish has some great stuff in there. But, in my case, 30 years of vi muscle memory was hard to blunt.