Ulrik,

Thanks for the suggestions and for the detailed rationale behind them.

Mapping as you describe it is already working for the next major release of ViEmu (there are other parts which aren't, that's why it isn't available yet). The only vim mapping feature not supported is multiple key chord mapping. So, I think you will be able to implement all those features without problems.

With regards to ViEmu getting back to command mode at most general events, I think a user setting will be necessary, as other users have requested the opposite behavior (it actually used to work like you describe in older versions, but I moved to the current model to follow vim's behavior).

I'll have a look at the Escape-swallowing problem. It shouldn't happen, and as far as I've noticed, it does not happen for me. Could you list which VS version you are using, and what (if any) other 3rd party plugins are installed?

Search highlighting is also due for the next major version, and the other features (proper buffer numbering, command line tab completion, and external filters) will also come in some time.

Thanks again!

Hm.... Ctrl-Y should actually scroll the window one line, in ViEmu the same as in vim (as long as Ctrl-Y has been unbound from any assignment in Tools|Options|Keyboard, else it will have that behavior). I also tried 'y' in visual mode, which does return to normal mode.

So I also tried Y in visual mode... and you're right, it had a bug. I've fixed it, 1.4.5-alpha-6:

  http://www.viemu.com/ViEmu145a6.msi

You need to manually uninstall the previous version before installing this one.

It also implements :clo[se] and Ctrl-W c to close the current window/split.

Thanks for the feedback!

You're most welcome. :-)

Great!

As long as I can get it to work like I want, e.g., via a user setting, I'm perfectly satisfied.

I use VS2005 with Visual Assist X 2005.11.25. True, the problem only occurs with Visual Assist enabled. But I've become pretty happy with Visual Assist, so I hope it can be made to work.

Superb!

Thank you!

I use ViEmu with DevExpress's CodeRush installed, and I've just installed Visual Assist to try it out.

After disabling a few features to stop it from clashing with DevExpress setup (which works perfectly with ViEmu BTW as long as you have nothing bound to Esc in their shortcuts menu), I noticed that Visual Assist is swallowing my escapes also -- which is a shame, because I really like the extended syntax highliting features - finally I can make everything look like 'elflord'!

Anyway, just thought I'd add my 0.02c.

I tend to turn all the refactoring stuff in CodeRush off, and refuse to install their Refactor package as it causes my IDE to slow to a crawl!

I am always interested fixes for CodeRush stuff (my manager spends a lot of time reporting bugs to them and talking to the dev team over their), so I'd like to get my hands on it if possible.

Johan,

Sure, download the following file:

  http://www.viemu.com/DXViEmuCompat.dll [Update May 25: the link was broken!]

and copy it into your DXCore plugins directory (typically c:\Program Files\Developer Express Inc\DXCore for Visual Studio .NET\1.1.\Bin\Plugins). You need to have ViEmu version 1.4.5-alpha-4 or later - the latest one is the following one:

  http://www.viemu.com/ViEmu145a7.msi

Which also fixes the cursor position after the :d command (you need to manually uninstall your current version of ViEmu before installing this one).

The net effect is that ViEmu will enter insert mode automatically when you use one of the CodeRush commands that enters "llinked identifier editing".

As always, I'm amazed by the randomness of the Visual Assist interaction problems. That only makes them more annoying and harder to fix.

BTW, the DevExpress people were very helpful in fixing the interaction, supplying a DXCore plugin skeleton from which I could detect the event. The customer who originally notified the problem also hacked it a bit until the behavior was perfect. All in all, a satisfying experience.

Jeff, thanks a lot for the feedback. ViEmu already goes to gret lenths to try to avoid VAX's auto-suggestion feature. It was the 1st thing I had to do. Here's the deal: both ViEmu and VAX subclass the editor window and filter keypresses, doing their things. Given that VAX assumes you are typing and brings up the autocompletion box, I try to subclass the window *after* VAX does. In that way, I can get hold of the keypress first, and not pass it on to VAX. How do I do I try to do it? I actually subclass the window *twice*, the first time quite early, but the second time actually only when an actual keypress or mouse action happens. The first subclassing doesn't do anything but show a block cursor (else it would be confusing) and trigger the second, 'real', subclassing.

For some reason that isn't clear to me, it seems this doesn't work reliably. I don't use VAX myself, so I only tested when I initially tried to address the compatibility problems.

I will try to get in touch with them directly and see if they can be of help - if they could point out exactly when they subclass the window, I could try to ensure I always do it afterwards. I'll let you know what comes up.

With regards to other features such as vi keybindings in their autocompletion window... I can't even know when it's been shown. Actually, not VS's own Intellisense let me know whether it's active...

Hi J,
I think that you may have answered this in a prior post in this thread, but I'd like to ask it explicitly anyway.

Would it be possible to have viemu ignore the first 'esc' if there is an intellisense popup? Right now if you want to type something that is not in intellisense and hit 'esc' you have to hit 'i' to get back to editing. If possible, then I'd suppose it'd certainly be a user preference thing...

thanks, nathan