Hi llimllib,

The key would be to use the ":vscmd" ViEmu command. Something like this:

:inoremap <tab> <esc>:vscmd {whatever}<return><i>

Should do the trick. You can use the command :macro to call a user macro (see the ViEmu documentation, there is a hotlink to your local copy in Tools|Options|ViEmu).

HTH,

  Jon

Cool, you're welcome.

Hello,

Why does it only work in insert mode? If it is because of the above mapping example (unsing :inoremap), then it is because "inoremap" is only honored in insert mode. You can use ":nnoremap" for normal mode, ":vnoremap" in visual mode, and there are others too (the documentation has them all, this is vim behavior actually).

For example, if you want do the same as above in normal mode, the line would be:

  :nnoremap <tab> :vscmd {whatever}<return>

I removed the <esc> (because we don't need to exit insert mode to call a : ex command from normal mode), and the 'i' to get back in insert mode.

Regards,

  Jon

Ok, as to why ":vscmd Smartcomplete" doesn't work, that one is easy: you need to provide a full command, the type of commands that work in the QuickFind combo box when preceded with '>' (this is not too well known, but it works). Thus, you need to use ":vscmd Macros.Smartcomplete" and that should work fine. You can also use the ViEmu shortcut ":macro", which prepends the "Macros." itself, so ":macro Smartcomplete" should work.

Regarding he fact that "Tab" by itself does nothing, how have you bound it to the macro? I'm not sure VS allows binding Tab (at least it doesn't allow me to enter it in Tools|Options|Keyboard). Knowing how you have bound it should help.

As to the autocompletion box not paying attention to input, it's normal that does happen if ViEmu is still in normal mode - autocompletion needs ViEmu to pass keypresses through, and it only does so in insert mode. If you're binding <tab> through ViEmu, it would definitely pay off to have an 'i' after ":macro ...<return>", to make ViEmu pass input through. Hopefully that will fix it.

Finally, regarding why the Tab is inserted in the wrong place, I'd need more details about how you have bound it and I'll try to understand what is happening.

VS<->ViEmu integration is pretty complex, as VS is not designed for such a radical change, and I handle all built-in cases in the code, but it's possibly necessary to do something more to do what you are trying to.

Ah ok. Yes, you need to prepend MyMacros and the module name to the macro invocation.

Regarding the questions: (1) is something I have asked the Microsoft VS developers quite a few times, and it seems there is no satisfactory answer at least on VS.NET 2003. VS2005 seems to have some support to detect it, but ViEmu is not using it. If I knew when it's open, I would be able to know about passing keys through instead of working in them, but it doesn't seem to work. In any case, since it's come up again, I'll have a look at it and get back to you about it.

Regarding (2) why cursor movement doesn't work, I'm not entirely sure. Can you test whether, if you leave out the <i> key from the mapping, it works? It won't work with the autocompletion box, but if the cursor movement works, I can probably find some solution to make it work. One possibility is adding a ViEmu macro command to be able to instruct it to enter insert mode from the macro - this is already accessible to other plug-ins through a VS service, but I could add another hook to call it from VS macros.