On Sat, Oct 10, 2009 at 1:08 PM, <[email protected]> wrote: ... > I often use a combo of "qq" (macro recording into register q) and > "@q" (execution of that macro via execution of the contents of > register q). ... > For that reas I did a > nmap <C-e> @q > in my ~/,vimrc (I am using vim with linux). > > A > :verbose map <C-e> > says that the mapping was last changed in ~/.vimrc and > maps to <C-e>. > So fine, so nice...but: > > If I press > <C-e> > vim waits in the commandline, displaying > :YR: Enter character: > > I think, that the Yankring-plugin (which I do love ;) > has intervented my mapping. But this in contradiction > to what > :verbose map <C-e> > tells me. > > Why does vim git stuck in the commandline expecting a character > from me and how can I map <C-e> without killing Yankring?
I gather the macro you recorded used one of the f, F, t, T motions. There is special code in the YankRing which checks to see if you are triggering a macro and if so, removes the expression maps for '@' so that you are not prompted again for the motion (f, F, t, T) which you recorded already. When you mapped <C-e> to @q, the YankRing looses the ability to check for this and you are left with the original issue of being re-prompted when the recorded macro is played back. It may be possible to allow you to set what key triggers a macro from your .vimrc. If I did that in the plugin then you would always have to use that key and never use the @ key. What are your thoughts on that? Dave --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
