Jason Imison
Jason Imison
This seems like it would be a good change. I didn't know about this feature and the old behaviour always used to catch me out.
I think the fix needs to go in [here](https://github.com/VsVim/VsVim/blob/3bc7ce5ba75e99e9add40d41a51e4382f18ec62d/Src/VimWpf/Implementation/RelativeLineNumbers/LineNumberFormatTracker.cs) if you'd like to have a go at it.
Worth noting that the Mac version of the addin correctly handles this https://github.com/VsVim/VsVim/blob/3bc7ce5ba75e99e9add40d41a51e4382f18ec62d/Src/VimMac/RelativeLineNumbers/RelativeLineNumbersMargin.cs#L135-L141 I guess the fix for Windows would be pretty similar (maybe the classification type name differs)
I think this is the same behavior as real Vim when `set number` has not been set. 
This was fixed by https://github.com/VsVim/VsVim/pull/3079
`VisualStudioVersion` is an Environment variable set by VS. You could check for that.
Or you could do something like `has("vim9script")` from VimScript
Please can you try temporarily disabling Windows Defender Antivirus if you are still able to reproduce this?
This PR seems very useful. Did you look to see how `vi"` works today? I'm not totally familiar with how this code works but it seems like it is using...
Check out my [example `~/vsvimrc` file](https://github.com/VsVim/VsVim/wiki/MacOS-guide#example-vim-configuration)... Especially the `set backspace` part