Vsvim: Macro recording with `q`, `Ctrl+n`, `Ctrl+p` and IntelliSense do not work together

[MartinL0815]

I had following macro to be recorded:

1. go to the first non-whitespace column (^)
2. change the complete line (C)
3. Enter UpdateToolBar();
4. quit macro recording

In step 3 I used IntelliSense to auto complete UpdateToolBar and entered the paranthesis and the semicolon manually.

Using the macro inserted UpdateTool, not the chosen UpdateToolBar!

So I re-recorded the macro using Ctrl+n, the Vim auto completion, but the result was not better at all.
With using the macro UpdateTol was inserted, instead of UpdateToolBar, because I mistyped the character l after hitting Ctrl+n, used Back to delete the mistyped character l letting VsVim auto complete to the correct text.

[jaredpar]

Intellisense is a constant problem for macro recording because of problems exactly like this. I'm beginning to wonder if it's a better idea to simply disable intellisense altogether during macro recording due to the inability to ever repeat it correctly

[MartinL0815]

Hi Jared,

but you realized, that, even if differently wrong, the behavior of the VsVim completion didn't satisfy macro recording?

Best regards,
Martin

[jaredpar]

@MartinLemburg are you referring to the Ctrl+N problem?

[MartinL0815]

Sure, no matter if using IntelliSense or VIM command completion with Ctrl-N/P, both let macro recording fail.

------- Original message -------

From: Jared Parsons [email protected]
To: [email protected]
Cc: martin.[email protected]
Sent: 14.7.'14, 22:24

@MartinLemburg are you referring to the Ctrl+N problem?

Reply to this email directly or view it on GitHub.

Martin Lemburg
Emdener Straße 19A
10551 Berlin
Deutschland

[phone] Mob.
[phone] Tel.
+49 3212 LEMBURG

martin.[email protected]
http://about.me/Martin0815

[dshook]

+1 for disabling intellisense and auto formatting while recording macros.

[damianpowell]

+1 for disabling Intellisense and auto formatting while recording macros.

I had used VsVim on and off for years but the final clincher that made me switch to it was when MS removed macros from Visual Studio. Vim macros are better than VS' old ones anyway, but fighting with Intellisense and auto formatting is a pain.