Rather than joining several actions, a different approach might be to allow the repeat register to be set explicitly, as if it were a macro.
Being able to read it would already be somewhat useful. See this reddit thread: http://www.reddit.com/r/vim/comments/1u5k0c/saving_the_last_normal_mode_command_so_command_to/. Arguably, it'd be a small benefit, but it's quite easy to do (I've been meaning to propose a patch for a while now). Being able to overwrite the `redobuff` would be even more useful, though, essentially replacing the entire repeat.vim plugin with: let @<redo-register> = "..." Right now, repeat.vim does a lot of tricks to work correctly and complicated usage of it can fail. I'm not sure how much easier it would make this particular use case, but maybe it's some starting point. It's somewhat similar to the "start a macro" advice, except there's no explicit macro, instead we store a more complicated movement as the "last action". For instance, it could be that pressing the "Left" key could store the current state of the redo buffer and cursor position in a variable, and register an autocommand for leaving insert mode when it stores the real "action to repeat". It might still turn out to be impossible or at least very complicated. Can't say without trying it out, maybe Dmitry can give his thoughts on this. -- -- You received this message from the "vim_dev" 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_dev" 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.
