VsVim / VsVim

Vim Emulator Plugin for Visual Studio 2015+
Other
3.66k stars 401 forks source link

Ctrl-F12 (GoToImplementation) puts VsVim into visual mode #2966

Open artemoks opened 2 years ago

artemoks commented 2 years ago

Describe the bug GoToImplementation puts VsVim into the visual mode.

To Reproduce Steps to reproduce the behavior:

  1. Set a cursor on a symbol
  2. Ctrl+F12
  3. VS jumps to the implementation and VsVim enters the visual mode

Expected behavior VsVim should stay in the command mode

Screenshots

Environment (please complete the following information):

Additional context Add any other context about the problem here.

Note: The following is written about contributing. https://github.com/VsVim/VsVim/blob/master/CONTRIBUTING.md

General Keyboard configuration problems are described below. https://github.com/VsVim/VsVim/issues/2527

mrubelmann commented 2 years ago

I've run into this in VS 2022 as well. It looks like it used to be a problem, was fixed, and has now come back: https://github.com/VsVim/VsVim/issues/1963

mezdelex commented 1 year ago

Definitely a problem I'm experiencing as well in VS2022.

TomMalitz commented 1 year ago

I am also experiencing this issue in VS2022.

hkleynhans commented 1 year ago

Also experiencing this is VS2022.

vcfvct commented 1 year ago

Same here, quite annoying. seems to be happening a while ago at #1963 ?

hkleynhans commented 1 year ago

Happening in C++ as well with Visual Assist.

coderguy57 commented 1 year ago

Same here. Is there no way of making a mapping that exits the visual mode? Something like this: :map gd :vsc Edit.GoToDefinition<CR><ESC> It doesn't work, but I guess the problem is that it presses ESC before it have gone to the definition. This could have been an ugly solution, but it doesn't seem like VsVim support :sleep :map gd :vsc Edit.GoToDefinition<CR>:sleep 100ms<ESC>

ghost commented 1 year ago

Same experience with C++ project editing

jackhub commented 1 year ago

I am also experiencing this issue in VS2022.

asuper0 commented 1 year ago

I am also experiencing this issue in VS2022, but only with C++. The C# project works well.