Let me say first of all I have no relationship with VsVim other than being a happy user.
It is utterly frustrating to me that because of bugs in one or the other I have to turn VsVim off half the time when using it with VaX.
Would you guys consider giving the VsVim developers a license for a couple of copies of VaX so that they can better support the case where they are installed together ? Their product is free and open source, so I would guess they are not inclined to buy the software themselves.
As an example, Araxis Merge gives out free licenses to open source contributors. It would be great if you guys could at least do that for VsVim :)
Well, I hit bugs every other day. The most annoying one recently was when I made corrections to a function parameter list CPP file using the "." vi command, the IDE was putting "." characters in the function declaration in the header. Since I never saw this before I had VaX, I must assume it's the combination of VsVim+VaX that causes it.
That being said, my point is not about specific bugs.
I know that quite a few people must use VsVim+VaX.
We could reduce the rigamarole around the user trying to figure out whose fault it is if we had the developers of VsVim able to test/repro with VaX.
quote:The most annoying one recently was when I made corrections to a function parameter list CPP file using the "." vi command, the IDE was putting "." characters in the function declaration in the header.
We will fix a few recently introduced problems in the next build. Can you please try our next build when it will be released and report back if this dot issue is solved?
For now, does unchecking the following setting prevent the problem for you? Tools | Options | Environment | Tabs and Windows | Preview Tab | Allow new files to be opened in the preview tab Go to Top of Page