1

Re: using ^o in insert mode to execute a command mode command doesn't work

I'm working on expanding my usage of vim and finding all the things that "irritate" me and make me shift modes more often, etc...

Anyway I found that ^o in insert mode will allow you to execute a single command mode command. This would be very helpful to support....

Thanks

2

Re: using ^o in insert mode to execute a command mode command doesn't work

Hi Ryan,

Apologies for the delay in answering. Indeed, ^O is not implemented in ViEmu. You are actually the second person to request this, the other person was someone just getting introduced to vi/vim editing - I mention this because it's significative, as many hundreds of customers have not missed it. I understand that ViEmu should provide it at some point for completeness sake, but I believe that the want of using ^O is often a sign of *not* using vi/vim editing correctly. If I may say so, I'd like to recommend you to read my article about vi/vim editing, as I deal with the most efficient way to use insert and normal modes:

  http://www.viemu.com/a-why-vi-vim.html

The main point covered there is that insert mode should be used just to insert short snippets of text, and one should go back to normal mode as quickly as possible. This is the most efficient way to use vi/vim editing, and if you do it that way, you don't miss ^O at all. I still haven't found a case where it's better to stay in insert mode and just issue an external command.

In any case, I take note of the request and I hope ViEmu will provide it at some point in the future, in which case I'll drop you a note about it.

And I hope you find my suggestion useful rather than disrespectful, as it's meant that way!

Best regards,

  Jon

3

Re: using ^o in insert mode to execute a command mode command doesn't work

Perhaps true, but i'm using viemu with whole tomato's visual assist and most of the time i have to hit esc twice to get out of insert mode (because many times the "autocomplete" feature has triggered, so one esc dismisses that and one gets back into insert mode) so i guess my internal keypress counter is triggering because:

<esc> <esc> p i

being twice as long as

<ctrl>-o p

maybe i'll try turning off autocomplete and map it to ctrl-p or something in insert mode..

4

Re: using ^o in insert mode to execute a command mode command doesn't work

Hmm... I remember implementing some "counter-measure" so that a single <esc> would do both things with Visual Assist installed (many customers use ViEmu with Visual Assist). If I remember right, you have to do :set vaxesc to turn the feature on (you can have that in _viemurc in your home directory and it would always be activated on startup).

Let me know how that works for you - and of course the request for ctrl-o still makes sense, even if only for completeness' sake!

5

Re: using ^o in insert mode to execute a command mode command doesn't work

works great!

Is there somewhere I could have found this? maybe a wiki or some other docs would be in order.. doxygen so you don't have to maintain a separate doc?

just a thought...

6

Re: using ^o in insert mode to execute a command mode command doesn't work

You can either go to the local documentation via Tools|Options|ViEmu -> "ViEmu documentation", or online at the following address:

   http://www.viemu.com/viemu_doc.html

There is also a page dedicated to 3rd party plug-in compatibility:

  http://www.viemu.com/viemu_compatibility.html

All of these are listed in the ViEmu/VS specific page, linked to from the main page as 'learn more':

  http://www.viemu.com/viemu-vi-vim-visual-studio.html

This last page is pretty ugly, I know. Making it nicer and clearer is on the todo list. Possibly the docs are not sufficiently prominent.

Regards,

  Jon