| T O P I C R E V I E W |
| pbrown |
Posted - Jul 20 2026 : 2:32:34 PM
I just upgraded to build 2615 and ran into a major problem when I started trying to use it.
I use the VsVim 2022 Visual Studio extension so that I can use Vim-style keybindings when editing my code. One Vim feature is visual selection, where you type "V" to start block selection and then use navigation commands to specify the extent of the block. Once a block is selected, you can use another command binding (e.g., delete, copy/paste, search/replace on each line) on the selected block.
When VsVim and VAX build 2615 are both enabled, Vim visual selection does not work. When I type the "V" command, the VsVim extension enables visual selection mode and displays "-- VISUAL --" on its bottom status line. However, once I trigger a navigation binding (e.g., "j" for moving down one line), the visual selection mode turns off. If I disable VAX via "Extensions -> VAssistX -> Enable/Disable Visual Assist", the Vim visual selection mode works fine.
Over the past few years, I have been bouncing back and forth between VAX and Resharper C++. I have been using Resharper recently but tried out the current VAX build over the weekend because of issues I've been having with Resharper recently. I'm definitely not jumping back to the current build of VAX due to this issue, which I don't recall seeing in prior builds. But I figured it would be a good idea to mention it since VsVim 2022 is a pretty popular extension. |
| 2 L A T E S T R E P L I E S (Newest First) |
| pbrown |
Posted - Jul 21 2026 : 09:54:11 AM
feline,
Thanks for attempting to reproduce. I did some more experiments and have concluded that you are definitely right that:
| it isn't as simple as just installing the current VA
I have Visual Studio 2019, 2022, and 2026 installed on my system but am primarily using 2026. I was able to reproduce the problem on VS2022 as well. I restored default settings for VAX by deleting various registry keys and also reset my Visual Studio 2026 settings. I also tried downgrading to VA 2588.0 (first version I found in my downloads folder). None of those changes solved this issue. I upgraded back to VA 2615.0 and the problem still persisted.
I was about to give up and abandon this report when I discovered something interesting with VA 2615.0 installed. When I type "v" while editing "file1.cpp", it enters visual selection mode. But it immediately exits selection mode when I type "j". The interesting thing is that if I switch to a second file "file2.cpp", visual selection mode works fine -- "v/j/j/j" highlights multiple lines as expected. When I switch back to "file1.cpp", visual selection continues to work. The same thing works in reverse. If I close and reopen Visual Studio while editing "file2.cpp", the restart shows "file2.cpp". As before, visual selection doesn't work. When I switch to "file1.cpp", visual selection starts working and continues working if I switch back to "file2.cpp".
*Very* strange.
By the way, I am also using VsVim 2.10.0.6 inside Visual Studio 2026 version 18.5.0. |
| feline |
Posted - Jul 21 2026 : 08:14:18 AM
Starting with VS2022, version 17.14.35 where VA has never been installed, under Windows 11, I first installed VsVim, version 2.10.0.6, and confirmed that V triggered block select, using both up and down arrow keys for whole lines, and 'j' and 'k' for vertical motion.
Then I installed VA 2615.0, and V is still working just fine for me. This is testing inside a cpp file.
I know we have a good number of users who work with both VsVim and VA together, although personally I found Vim and Visual Studio to be so different I can either use one or the other, but not both together.
Whatever the trigger for the problem you are seeing is, it isn't as simple as just installing the current VA alongside the current VsVim.
|
|
|
