On Mon, Nov 16, 2015 at 12:41 PM, Christian Brabandt <[email protected]> wrote: > > So how about adding some warning into the documentation that putting from the > same register that is used for recording won't likely work as one would > expect and perhaps also mention in the status line which register is used for > recording (e.g. instead of "recording" use "recording @a" or similar, > possibly with an 'shortmess' option to disable it)? Would that be an > acceptable compromise?
I think it would. OTOH, an are-you-sure prompt or an exception halfway through the recording might change what is recorded and/or break existing scripts unless coded with due attention to all possible corner cases, so IMHO that would be much more problematic. Best regards, Tony. -- -- 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.
