Vsvim: Linebreaks and backspace in macros

[ahem]

In VSVim 1.3.1.3 macros doesn't record special characters like linebreaks and backspace. I seem to recall this working in previous versions, but I may be mistaken. If I record this macro: 9lf,a"<ENTER>+ " in vsvim, then the enter key is not recorded. If I do the same in Vim it is - if I paste the recorded macro in Vim I get this output:

9lf,a"^M+ "^[

In vsvim the same macro is pasted like this:

9lf,a"+ "

When I execute the macro, the newline is missing as well.

[jaredpar]

Thanks for reporting!

That definitely should be getting recorded. I have a suspicion where that regression could come from. Will investigate.

[jaredpar]

Want to try and clarify something. When you say that the <Enter> key isn't recorded do you mean that it doesn't repeat in the macro playback or just doesn't show up in the paste? I can definitely see it getting repeated but it isn't showing up as expected in the output. It's in the output but I have a bug that causes it to paste differently than gVim would. Working on that.

[ahem]

I am not seeing the enter key repeated as well - that is the issue, mostly. I just noticed that it wasn't written out when I pasted the register in an attempt to debug why the macro wasn't being replayed correctly. Actually it seems like the enter key isn't being recorded at all.

I have disabled resharper and every autocomplete option in visual studio in an attempt to work around this issue, but it doesn't seem to make any difference. I also have tried to remove my .vimrc file but that doesn't make any difference either.

This is mysterios - I am sure this used to work, and if it works on your end, then maybe I am the only one who has this issue? That just seems plain weird.

I am using Visual Studio 2010 Professional with Service Pack 1 on Windows 7 and VSVim 1.3.1.3

[jaredpar]

It sounds like it's potentially R# interferring. I'll test that theory out tonight

[neeasade]

Also seeing backspace not working in macros.

[jaredpar]

This should be fixed in the next version of VsVim (release early next week). There is a new setting that causes VsVim to have much stricter macro recording. That will fix issues like this.

[neeasade]

Awesome, thanks!

[ricksladkey]

Fixed by the "Clean Macro Recording" setting.