Rick Howe wrote:
> > > My plugin has a similar event settings and does not work on 8.1.256. > > > > It's expected that the patch slightly changes undo behavior, especially > > if you do something weird like using undo in an autocommand. The change > > is needed to avoid corruption of undo. > > Yes, it is something weird but in order to check which lines were changed, > no other way exists. > > > So it's different, but why would it be wrong or bad? > > I am not sure but I have to change my plugin anyway. > Please help me understand why changenr() becomes 2, not 1, so that > I can implement a better workaround. > And, as far as I know, TextChanged is not affected, right? The code in edit() assumes the current line has been saved for undo, that it adds another line when needed (e.g. backspacing over a line break). However, if an autocommand touched undo info, the assumption was not true, that is fixed now. That des mean a new undo block is created, thus the change number increases. -- "Hit any key to continue" is very confusing when you have two keyboards. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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.
