Re: Keyboard management bug
I just uninstalled the first 2.0 build and installed 2.0.34 and figured I'd try to get my saved keybindings set up correctly (I use ViEmu at work, so when others use my computer I have to turn off ViEmu and turn it back on again relatively frequently), but in doing so I ran into a bug (or at least, I'm not sure what the desired behavior is).
Basically I want to have my saved keybindings include all the default ones that clash with VS, and ctrl-o and ctrl-d for workspace whiz (the wwhiz file open and tag dialog). So I assigned the wwhiz keys before I reinstalled, and then installed 2.0.34. After starting VS, it had correctly saved the VS binds, but left the wwhiz binds as clashing. Seeing as I wanted the wwhiz binds removed also, I hit save and remove, but this caused all the VS saved keybindings to disappear... I'm not sure how to get them back at this point (my VS "reset to default settings" seems to also be broken, but I don't think this has anything to do with ViEmu)
I guess I assumed that if I hit save and remove it would add the list of clashing bindings to the saved keybindings, is this not the case?
I also noticed that when I turn off ViEmu in one VS, and then start another, the "clashing keybindings" message comes up... Is there some way ViEmu could globally turn itself on and off so that starting a new VS would not pop up this message? If not, what is the ideal way to deal with this but maintain my current settings? Just hit "no don't bring up the dialog"?
Then, as a feature request, is it possible to get ]p to work with the new engine? I would love to be able to use that Also, is there any chance that 2.1 will have the "surround selection" visual assist feature I mentioned in another thread?
Sorry for the long rambling list of feedback/requests, ViEmu really is awesome