On Thursday, July 19, 2018 at 7:35:22 AM UTC+12, Bill Tugger wrote: I'm not sure the other responders are really addressing your question.
> I'd like to also have the repeat command (.) be remembered. Actually, IIUC, no. See :help 'viminfo' for what can be saved. Note that "registers" are saved, and registers are where recorded macros go, so, one work-flow that might suit you is to record macros for the changes you make. But, I suggest a solution would be to *not exit vim* after each file. Naybe use the arg list, so :w then :n to the next file, and . will work nicely. If there are several changes, :rewind the list for each change. If the list of files can't be determined at the beginning of a session, after writing a file, :e the next, or use drag and drop in a GUI. I suppose you're really asking for vim to always record to, say, the "unnamed" macro, so that the viminfo mechanism could save and restore it. I googled for "vim automatic macro record" and "vim always record macro" with no pertinent results; I thought maybe someone had done a plugin to simulate it. Regards, John Little -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
