I almost forgot.  This time I'm using ViEmu version 1.5.1 on Windows XP Professional with Microsoft Word 2003 SP3.

Apologies Brent, I've been overly busy lately and it's taking me longer to respond.

Indeed, ViEmu in Word can be very slow with large or otherwise "problematic" documents. There is not much that can't be done. This is due to Word's underlying object model, which ViEmu uses, and which is excruciatingly slow for even simple things like asking for the number of paragraphs (which ViEmu often has to do, as there are no notifications or other event triggers to know when the document has been updated!). ViEmu uses a quite complex caching system to try to minimize this, but the caching system is only efficient for simpler or smaller documents. This is not noticeable while typing (thanks to some internal ViEmu optimizations) or while moving around in normal mode, but it's most noticeable either when focus changes (ViEmu assumes the cache might be invalid now), or when switching from insert mode to normal mode or back.

I'd think that the table of contents might be the culprit in this case, but it might be something else.

Unfortunately, there is not much that I can do before Microsoft implements some better extensibility model (unlikely), or we all move to a better architected word processor (even more unlikely yet).

Best regards,

  Jon

Hello,

The comment about moving to another word processor was somewhat tongue-in-cheek... At least in principle, I don't really plan to implement other ViEmu editions. The reason is that the required effort is huge, and the economies of scale don't really kick in to make it worthwhile.

On the other hand, I seem to remember that someone had at least started implementing a vi input mode for the open source word processor AbiWord, although I don't know how functional it was.

Best regards,

  Jon