|
pbrown
Senior Member
USA
45 Posts |
 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. |
|
VA Build 2615 breaks VsVim visual selection
