vi mode missing

[arael]

Maybe I overlooked in the documentation but it seems to me that the vi mode is missing. I think that fish shell is awesome but without the vi mode I cannot use it as my everyday shell. Is there any way to enable the vi mode in fish right now?

Maybe it is possible to achieve this through the configuration somehow although I have doubts. It is more likely that this is a missing feature.

Thank you very much for all your work.

[jonsterling]

I think this is on the list of planned features somewhere…

[jonsterling]

I think this is on the list of planned features somewhere…

[SebastianThorn]

what is vi mode suppose to do?

[SebastianThorn]

what is vi mode suppose to do?

[arael]

Emacs is a powerful text editing program. Usually the default for all shells is the emacs mode. This means that the command line editing can be performed by using emacs shortcuts. So Ctrl-a puts the cursor on the beginning of the line and Ctrl-e on the end of the line. Alt-f advances the cursor forward word by word while Alt-b works in reverse. Alt-d cuts a word and Ctrl-y pastes it etc. If you know emacs you can use most of its keyboard shortcuts to edit your command line.

Vi/Vim is also a text editor program. The vi mode has its own set of shortcuts and it is modal. There is the normal or command mode and the insert mode. The command mode is used to browse the history and perform command line editing just like in vi. The insert mode is meant to insert text. So in the normal mode pressing 0 puts the cursor on the beginning of the line while $ puts it at the end. You can advance between words by pressing w or e and cut words by pressing cw (change word). Pressing p pastes the word back etc. The vi mode is very useful for people using vi/vim as their default editor. It is quite efficient if you know vi.

If you are interested I suggest you to search on web more info about the subject. Knowing how to move efficiently on your command line is useful and interesting and most importantly more productive.

[arael]

Emacs is a powerful text editing program. Usually the default for all shells is the emacs mode. This means that the command line editing can be performed by using emacs shortcuts. So Ctrl-a puts the cursor on the beginning of the line and Ctrl-e on the end of the line. Alt-f advances the cursor forward word by word while Alt-b works in reverse. Alt-d cuts a word and Ctrl-y pastes it etc. If you know emacs you can use most of its keyboard shortcuts to edit your command line.

Vi/Vim is also a text editor program. The vi mode has its own set of shortcuts and it is modal. There is the normal or command mode and the insert mode. The command mode is used to browse the history and perform command line editing just like in vi. The insert mode is meant to insert text. So in the normal mode pressing 0 puts the cursor on the beginning of the line while $ puts it at the end. You can advance between words by pressing w or e and cut words by pressing cw (change word). Pressing p pastes the word back etc. The vi mode is very useful for people using vi/vim as their default editor. It is quite efficient if you know vi.

If you are interested I suggest you to search on web more info about the subject. Knowing how to move efficiently on your command line is useful and interesting and most importantly more productive.

[jonsterling]

That was a hell of an answer! Cheers.

Sent from my iPhone

On Jun 9, 2012, at 1:56 AM, Goran Josicreply@reply.github.com wrote:

Emacs is a powerful text editing program. Usually the default for all shells is the emacs mode. This means that the command line editing can be performed by using emacs shortcuts. So Ctrl-a puts the cursor on the beginning of the line and Ctrl-e on the end of the line. Alt-f advances the cursor forward word by word while Alt-b works in reverse. Alt-d cuts a word and Ctrl-y pastes it etc. If you know emacs you can use most of its keyboard shortcuts to edit your command line.

Vi/Vim is also a text editor program. The vi mode has its own set of shortcuts and it is modal. There is the normal or command mode and the insert mode. The command mode is used to browse the history and perform command line editing just like in vi. The insert mode is meant to insert text. So in the normal mode pressing 0 puts the cursor on the beginning of the line while $ puts it at the end. You can advance between words by pressing w or e and cut words by pressing cw (change word). Pressing p pastes the word back etc. The vi mode is very useful for people using vi/vim as their default editor. It is quite efficient if you know vi.

If you are interested I suggest you to search on web more info about the subject. Knowing how to move efficiently on your command line is useful and interesting and most importantly more productive.

---

Reply to this email directly or view it on GitHub:
https://github.com/ridiculousfish/fishfish/issues/65#issuecomment-6218113

[jonsterling]

That was a hell of an answer! Cheers.

Sent from my iPhone

On Jun 9, 2012, at 1:56 AM, Goran Josicreply@reply.github.com wrote:

Emacs is a powerful text editing program. Usually the default for all shells is the emacs mode. This means that the command line editing can be performed by using emacs shortcuts. So Ctrl-a puts the cursor on the beginning of the line and Ctrl-e on the end of the line. Alt-f advances the cursor forward word by word while Alt-b works in reverse. Alt-d cuts a word and Ctrl-y pastes it etc. If you know emacs you can use most of its keyboard shortcuts to edit your command line.

Vi/Vim is also a text editor program. The vi mode has its own set of shortcuts and it is modal. There is the normal or command mode and the insert mode. The command mode is used to browse the history and perform command line editing just like in vi. The insert mode is meant to insert text. So in the normal mode pressing 0 puts the cursor on the beginning of the line while $ puts it at the end. You can advance between words by pressing w or e and cut words by pressing cw (change word). Pressing p pastes the word back etc. The vi mode is very useful for people using vi/vim as their default editor. It is quite efficient if you know vi.

If you are interested I suggest you to search on web more info about the subject. Knowing how to move efficiently on your command line is useful and interesting and most importantly more productive.

---

Reply to this email directly or view it on GitHub:
https://github.com/ridiculousfish/fishfish/issues/65#issuecomment-6218113

[arael]

=)

[arael]

=)

[SebastianThorn]

okey, been using emacs all my life and i never thought of the vi/m isers around the world ;)

[SebastianThorn]

okey, been using emacs all my life and i never thought of the vi/m isers around the world ;)

[silenc3r]

If you plan to make vi mode, please make it display current mode (command/insert/visual). As much as I like vim I find vi mode in shell extremly annoying and unusable since I never know which mode I am in.

[silenc3r]

If you plan to make vi mode, please make it display current mode (command/insert/visual). As much as I like vim I find vi mode in shell extremly annoying and unusable since I never know which mode I am in.

[arael]

@SebastianThorn We are out there brother. ;)

@silenc3r That is an excellent suggestion. I highly second that.
In bash I have the same problem. Pressing i first has become an habit of mine. This would be very useful to have in fish.

[arael]

@SebastianThorn We are out there brother. ;)

@silenc3r That is an excellent suggestion. I highly second that.
In bash I have the same problem. Pressing i first has become an habit of mine. This would be very useful to have in fish.

[paidhi]

I second that.
The missing vi-mode was the one thing keeping me from using the original fish shell.
"Complete vi-mode key bindings" was in the manual section of "Missing features" forever.

[paidhi]

I second that.
The missing vi-mode was the one thing keeping me from using the original fish shell.
"Complete vi-mode key bindings" was in the manual section of "Missing features" forever.

[kalikiana]

There's an interesting implementation of this being developed on the mailing list: http://sourceforge.net/mailarchive/message.php?msg_id=29431816

[kalikiana]

There's an interesting implementation of this being developed on the mailing list: http://sourceforge.net/mailarchive/message.php?msg_id=29431816

[arael]

It is not complete yet but it is functional actually.

[arael]

It is not complete yet but it is functional actually.

[JeanMertz]

@kalikiana Thank you for that link. I got it working and it looks nice. However, it's not on-par with the zsh vi-mode yet.

It also seems pretty slow. Actions like jump back one word have a lag of a few hundred milliseconds.

This script surely seems like a good start, but with the slowness I guess it can become somewhat annoying if you use it on a daily basis.

[JeanMertz]

@kalikiana Thank you for that link. I got it working and it looks nice. However, it's not on-par with the zsh vi-mode yet.

It also seems pretty slow. Actions like jump back one word have a lag of a few hundred milliseconds.

This script surely seems like a good start, but with the slowness I guess it can become somewhat annoying if you use it on a daily basis.

[hauleth]

👍

[hauleth]

👍

[davidrivers]

zomg +1

[davidrivers]

zomg +1

[amitkot]

+1

[amitkot]

+1

[nocksock]

How's the status on this?

[nocksock]

How's the status on this?

[arael]

Well, there is nothing in the release notes yet so I guess the vi-mode is still missing. You can check here:
http://www.ridiculousfish.com/shell/release_notes.html

[arael]

Well, there is nothing in the release notes yet so I guess the vi-mode is still missing. You can check here:
http://www.ridiculousfish.com/shell/release_notes.html

[ridiculousfish]

I'm not aware of any work being done on this, though obviously it's highly desired.

I'd like to do it but I'm not a vi user, so it'll take me a while to ramp up. On the other hand it makes an excellent excuse to learn.

[ridiculousfish]

I'm not aware of any work being done on this, though obviously it's highly desired.

I'd like to do it but I'm not a vi user, so it'll take me a while to ramp up. On the other hand it makes an excellent excuse to learn.

[JeanMertz]

I would love to see this become a reality!

On Mon, Feb 18, 2013 at 10:09 PM, ridiculousfish notifications@github.com
wrote:

I'm not aware of any work being done on this, though obviously it's highly desired.

I'd like to do it but I'm not a vi user, so it'll take me a while to ramp up. On the other hand it makes an excellent excuse to learn.

Reply to this email directly or view it on GitHub:
#65 (comment)

[JeanMertz]

I would love to see this become a reality!

On Mon, Feb 18, 2013 at 10:09 PM, ridiculousfish notifications@github.com
wrote:

I'm not aware of any work being done on this, though obviously it's highly desired.

I'd like to do it but I'm not a vi user, so it'll take me a while to ramp up. On the other hand it makes an excellent excuse to learn.

Reply to this email directly or view it on GitHub:
#65 (comment)

[maxfl]

There is a partial implementation of vi-mode here. It's not updated currently.
https://raw.github.com/DarkStarSword/junk/master/vi-mode.fish

@ridiculousfish, I think one of the main obstacles which makes it difficult to introduce a vi-mode is the lack of bind modes: the ability to quickly switch a current set of bound keys to another one is highly desirable. Introducing it will greatly simplify extension of vi-mode bindings by the ordinary users.
I mean something like this:

bind -m vi-normal i 'some action' # for the key 'i' to work only in vi-normal mode
bind -m vi-normal # to switch to the vi-normal mode, where only 'i' key is defined

There was a message by Ian Munsie (the author of the vi-mode) on a fish shell mailing list with a feature request he needed for his implementation of the vim mode. They might be still relevant:

For the suggestion of an option to catch the next symbol, I think that bind '' func would be enough if func can determine which key was pressed. Passing the key in as a parameter would make sense, but would likely break existing code, so perhaps a special variable could be introduced for this purpose? If there is already a way to do this that I've missed let me know, but as far as I can tell self-insert is the only function that can do this.

There is still also the caveat that if '' is not bound to self-insert then commandline -f repaint doesn't repaint the prompt, which would need to be fixed before I could make use of it.

Another feature I'd like is a way to temporarily suppress the auto-suggestion feature. It's a bit out of place in vi normal mode, and can obscure the results of the change-case commands if a suggestion is already being displayed. I see there is already a suppress_autosuggestion variable which is set when pressing backspace - it would be great if I could set that with something like commandline -f suppress_autosuggestion when leaving insert mode. I personally don't mind whether I have to explicitly re-enable it or just wait until it is implicitly re-enabled next time a character is
inserted.

Cheers,
-Ian

[maxfl]

There is a partial implementation of vi-mode here. It's not updated currently.
https://raw.github.com/DarkStarSword/junk/master/vi-mode.fish

@ridiculousfish, I think one of the main obstacles which makes it difficult to introduce a vi-mode is the lack of bind modes: the ability to quickly switch a current set of bound keys to another one is highly desirable. Introducing it will greatly simplify extension of vi-mode bindings by the ordinary users.
I mean something like this:

bind -m vi-normal i 'some action' # for the key 'i' to work only in vi-normal mode
bind -m vi-normal # to switch to the vi-normal mode, where only 'i' key is defined

There was a message by Ian Munsie (the author of the vi-mode) on a fish shell mailing list with a feature request he needed for his implementation of the vim mode. They might be still relevant:

For the suggestion of an option to catch the next symbol, I think that bind '' func would be enough if func can determine which key was pressed. Passing the key in as a parameter would make sense, but would likely break existing code, so perhaps a special variable could be introduced for this purpose? If there is already a way to do this that I've missed let me know, but as far as I can tell self-insert is the only function that can do this.

There is still also the caveat that if '' is not bound to self-insert then commandline -f repaint doesn't repaint the prompt, which would need to be fixed before I could make use of it.

Another feature I'd like is a way to temporarily suppress the auto-suggestion feature. It's a bit out of place in vi normal mode, and can obscure the results of the change-case commands if a suggestion is already being displayed. I see there is already a suppress_autosuggestion variable which is set when pressing backspace - it would be great if I could set that with something like commandline -f suppress_autosuggestion when leaving insert mode. I personally don't mind whether I have to explicitly re-enable it or just wait until it is implicitly re-enabled next time a character is
inserted.

Cheers,
-Ian

[trevor]

👍

[trevor]

👍

[nagisa]

I'm waiting for this too.

[nagisa]

I'm waiting for this too.

[vially]

👍

[vially]

👍

[oelmekki]

+1

I've just discovered fish and it seems great. But using bash in vi-mode for years make it a deal breaker for me.

Nobody mentioned it, but vi-mode is not a bash or zsh feature (provided they did not rewrote it totally), it's a readline feature : http://cnswww.cns.cwru.edu/php/chet/readline/readline.html#SEC22

I see a few readline references in codebase, but mostly about a "inject readline function" option, so I'm not sure if fish use readline. If it does, I suppose we could have a basic support by switching its mode to vi on fish init. I'm afraid it's not the case, though, as setting set editing-mode vi in ~/.inputrc does not affect fish.

[oelmekki]

+1

I've just discovered fish and it seems great. But using bash in vi-mode for years make it a deal breaker for me.

Nobody mentioned it, but vi-mode is not a bash or zsh feature (provided they did not rewrote it totally), it's a readline feature : http://cnswww.cns.cwru.edu/php/chet/readline/readline.html#SEC22

I see a few readline references in codebase, but mostly about a "inject readline function" option, so I'm not sure if fish use readline. If it does, I suppose we could have a basic support by switching its mode to vi on fish init. I'm afraid it's not the case, though, as setting set editing-mode vi in ~/.inputrc does not affect fish.

[trevor]

good find @oelmekki, all new to me

[trevor]

good find @oelmekki, all new to me

[dag]

I'm not convinced vi-style really works well for a command line, even though you could consider me a hardcore Vim user. It's really shitty in readline, and actually even in Vim I use vim-rsi to get the default readline bindings in Insert and Command mode, because they're just better for single-line input with minor editing, which is what you tend to do in a shell. However, fish actually makes multi-line commands more useful, so things might be different in fish. If we do this in fish, I think it's important that we avoid the limitations of vi-mode in readline, which for me means making it clear which mode you're in (such as by putting it in the prompt and repainting it on mode changes, and/or in the terminal title) and that it supports Vim's features for multi-line editing and the operator-pending mode. That means things like ciw and da( should work and that jk moves between lines, etc. None of those work or do the right thing in readline's vi-mode. Proper support for repeat (with .) is also rather telling about the quality of a vim imitation.

However I'm not sure if having two completely different key bindings supported is in line with fish's design philosophy. Might be fine to extend bind with the necessary features to make this possible in a third-party script though.

[dag]

I'm not convinced vi-style really works well for a command line, even though you could consider me a hardcore Vim user. It's really shitty in readline, and actually even in Vim I use vim-rsi to get the default readline bindings in Insert and Command mode, because they're just better for single-line input with minor editing, which is what you tend to do in a shell. However, fish actually makes multi-line commands more useful, so things might be different in fish. If we do this in fish, I think it's important that we avoid the limitations of vi-mode in readline, which for me means making it clear which mode you're in (such as by putting it in the prompt and repainting it on mode changes, and/or in the terminal title) and that it supports Vim's features for multi-line editing and the operator-pending mode. That means things like ciw and da( should work and that jk moves between lines, etc. None of those work or do the right thing in readline's vi-mode. Proper support for repeat (with .) is also rather telling about the quality of a vim imitation.

However I'm not sure if having two completely different key bindings supported is in line with fish's design philosophy. Might be fine to extend bind with the necessary features to make this possible in a third-party script though.

[oelmekki]

@dag Well, your proposition is surely interesting, and I would be glad if this happens. But just to be clear, I would love to have an implementation as "shitty" as readline's one instead of nothing, if your view of correct implementation happens to be too difficult to realize.

[oelmekki]

@dag Well, your proposition is surely interesting, and I would be glad if this happens. But just to be clear, I would love to have an implementation as "shitty" as readline's one instead of nothing, if your view of correct implementation happens to be too difficult to realize.

[arael]

same here. I really like the suggestions dag made and it would be great to have that implemented but I would settle with the readline support gladly.

[arael]

same here. I really like the suggestions dag made and it would be great to have that implemented but I would settle with the readline support gladly.

[dag]

I sympathize but I think that way lies zsh: there's a feature or configuration option for everything, but nothing feels quite complete or thought out. fish on the other hand tries hard to not make anything an option (but of course it's unavoidable) and to prefer quality features over quantity. But at the same time I think that fish tries to be highly customizable, which isn't the same thing as configurable. What I mean is that it provides the tools to let you easily script any feature you want. Take for instance my recent comment over in #128. That's what I'm after with extending bind without adding a vi mode option in fish core.

[dag]

I sympathize but I think that way lies zsh: there's a feature or configuration option for everything, but nothing feels quite complete or thought out. fish on the other hand tries hard to not make anything an option (but of course it's unavoidable) and to prefer quality features over quantity. But at the same time I think that fish tries to be highly customizable, which isn't the same thing as configurable. What I mean is that it provides the tools to let you easily script any feature you want. Take for instance my recent comment over in #128. That's what I'm after with extending bind without adding a vi mode option in fish core.

[trevor]

re: What annoys me a lot in bash: there is no way to determine what is the current mode you are using.

They could switch to vim zsh.

[trevor]

re: What annoys me a lot in bash: there is no way to determine what is the current mode you are using.

They could switch to vim zsh.

[Slava]

@trevor

Hi, can you tell me more on what you mean here?

My use-case:

1. I switch back to some tab or screen tab or just different terminal window
2. I don't remember (and I can't) what was the last state of the command line (normal or insert)
3. To switch to vim (edit current line in vim) I need to press 'v' from the normal mode
4. Since I don't know what is the current mode, I would tap ESC and then press 'v' but it is not better than just switching to normal mode every time (exactly the thing that annoys me).

[Slava]

@trevor

Hi, can you tell me more on what you mean here?

My use-case:

1. I switch back to some tab or screen tab or just different terminal window
2. I don't remember (and I can't) what was the last state of the command line (normal or insert)
3. To switch to vim (edit current line in vim) I need to press 'v' from the normal mode
4. Since I don't know what is the current mode, I would tap ESC and then press 'v' but it is not better than just switching to normal mode every time (exactly the thing that annoys me).

[trevor]

@Slava

I mistyped - make that "They could switch to zsh.", Sorry.

http://stackoverflow.com/questions/3622943/zsh-vi-mode-status-line
http://hamberg.no/erlend/posts/2010-10-17-show-current-vi-mode-in-zsh-prompt.html
http://unix.stackexchange.com/questions/547/make-my-zsh-prompt-show-mode-in-vi-mode
http://archlinux.me/w0ng/2012/04/06/zsh-change-cursor-colour-to-indicate-vi-mode/

[trevor]

@Slava

I mistyped - make that "They could switch to zsh.", Sorry.

http://stackoverflow.com/questions/3622943/zsh-vi-mode-status-line
http://hamberg.no/erlend/posts/2010-10-17-show-current-vi-mode-in-zsh-prompt.html
http://unix.stackexchange.com/questions/547/make-my-zsh-prompt-show-mode-in-vi-mode
http://archlinux.me/w0ng/2012/04/06/zsh-change-cursor-colour-to-indicate-vi-mode/

[Gonzih]

Any changes on that question? Would love to use vi mode in fish!

[Gonzih]

Any changes on that question? Would love to use vi mode in fish!

[pirj]

Bottom line:
Issue reopened.
There are couple different ways on how to implement this.
Milestone is fish-future which means:

These are bugs that are not targeted for an upcoming release. If you can provide a fix for a bug in this milestone, we'll generally accept it for the next release even if the bug is not in the release.

+1's do not work.
Please help if you're a good C coder and can submit a patch.

[pirj]

Bottom line:
Issue reopened.
There are couple different ways on how to implement this.
Milestone is fish-future which means:

These are bugs that are not targeted for an upcoming release. If you can provide a fix for a bug in this milestone, we'll generally accept it for the next release even if the bug is not in the release.

+1's do not work.
Please help if you're a good C coder and can submit a patch.

[xfix]

@pirj: I'm going to confirm this. Make a good patch, submit it, and it will be accepted for next fish shell release. fish-future is intentional - it isn't high priority (because it's relatively complex), but that doesn't mean developers don't want this feature. The patch implementing bind modes, or something like that would be preferred.

[xfix]

@pirj: I'm going to confirm this. Make a good patch, submit it, and it will be accepted for next fish shell release. fish-future is intentional - it isn't high priority (because it's relatively complex), but that doesn't mean developers don't want this feature. The patch implementing bind modes, or something like that would be preferred.

[syl20bnr]

For those who cannot wait the official vi-mode for fish I submitted a vi-mode plugin into the oh-my-fish repo: bpinto/oh-my-fish#107
The vi key bindings support is basic but I plan to improve it a bit. See the README for more info.

[syl20bnr]

For those who cannot wait the official vi-mode for fish I submitted a vi-mode plugin into the oh-my-fish repo: bpinto/oh-my-fish#107
The vi key bindings support is basic but I plan to improve it a bit. See the README for more info.

[furunkel]

You might be interested in this: #1218.

[furunkel]

You might be interested in this: #1218.

[roytruelove]

+1

[roytruelove]

+1

[vikstrous]

+1

[vikstrous]

+1

[xfix]

Fixed by applying #1218. This is not an April Fools' joke. Now the +1 flood can stop. If you want to test new vi mode, download the newest master, and run fish_vi_key_bindings. You can also use fish_vi_prompt to see the current status (or use $fish_bind_mode directly). There are still some issues, like #1387, but the basic support for vi bindings now exists.

@furunkel: Feel free to apply for $200 at https://www.bountysource.com/issues/986070-vi-mode/bounties. You probably are aware of this bounty, if you read this topic, but I mention this just in case. I believe your patch wasn't easy to make anyway, so you definitely deserve this bounty from the community.

[xfix]

Fixed by applying #1218. This is not an April Fools' joke. Now the +1 flood can stop. If you want to test new vi mode, download the newest master, and run fish_vi_key_bindings. You can also use fish_vi_prompt to see the current status (or use $fish_bind_mode directly). There are still some issues, like #1387, but the basic support for vi bindings now exists.

@furunkel: Feel free to apply for $200 at https://www.bountysource.com/issues/986070-vi-mode/bounties. You probably are aware of this bounty, if you read this topic, but I mention this just in case. I believe your patch wasn't easy to make anyway, so you definitely deserve this bounty from the community.

[arael]

Thank you very much!

[arael]

Thank you very much!

[oelmekki]

Awesome, thanks !

Now the +1 flood can stop.

By the way, if this annoys you, make sure to report it to github. A +1
feature on issues is long overdue, and all popular open source
repositories are annoyed by this.

[oelmekki]

Awesome, thanks !

Now the +1 flood can stop.

By the way, if this annoys you, make sure to report it to github. A +1
feature on issues is long overdue, and all popular open source
repositories are annoyed by this.

[jstrater]

Thank you, @furunkel!

[jstrater]

Thank you, @furunkel!

[catalan42]

OMG this is soooooo cool! And just in time, too!

[catalan42]

OMG this is soooooo cool! And just in time, too!

[rappo]

The $200 bounty that was posted on this issue waiting to be claimed, @furunkel :)
https://www.bountysource.com/issues/986070-vi-mode-missing/developers

[rappo]

The $200 bounty that was posted on this issue waiting to be claimed, @furunkel :)
https://www.bountysource.com/issues/986070-vi-mode-missing/developers

[Gonzih]

Is there any information on when this feature will be included in release? I don't see it in 2.1.1.

[Gonzih]

Is there any information on when this feature will be included in release? I don't see it in 2.1.1.

[zanchey]

It will be in the next minor release (2.2.0).

[zanchey]

It will be in the next minor release (2.2.0).

[Gonzih]

Ugh, I just updated fish nightly on my machine to the version fish, version 2.1.2-1247-gfbe28fd and now after command execution vim mode always jumps in to insert mode. I have hard times understanding what has changed. Any tips? Thank you.

[Gonzih]

Ugh, I just updated fish nightly on my machine to the version fish, version 2.1.2-1247-gfbe28fd and now after command execution vim mode always jumps in to insert mode. I have hard times understanding what has changed. Any tips? Thank you.

[vially]

Most probably this has changed.

[vially]

Most probably this has changed.

[Gonzih]

Ok, it's related to the #1933 issue. I actually don't like this change, feels weird. Not sure that blindly mimicking vim mode from zsh is a good idea on it's own. I will erase this binding in my configuration, not a problem.

Thanks for pointing this out, @vially

[Gonzih]

Ok, it's related to the #1933 issue. I actually don't like this change, feels weird. Not sure that blindly mimicking vim mode from zsh is a good idea on it's own. I will erase this binding in my configuration, not a problem.

Thanks for pointing this out, @vially

[ridiculousfish]

How do other vi-mode users feel about switching to insert mode after command execution? I merged that because it's what bash and zsh do, so I assumed it would feel natural, but maybe I was mistaken.

[ridiculousfish]

How do other vi-mode users feel about switching to insert mode after command execution? I merged that because it's what bash and zsh do, so I assumed it would feel natural, but maybe I was mistaken.