Philippe Vaucher wrote: > > I think they should be called TextDeletePost and TextYankPost to be > > consistent. > > Ok, I can do that. > > > Try doing something weird in the autocommand, such as "help" and then > > deleting something. > > You probably need to disallow lots of things to avoid breaking stuff > > (and perhaps even crashing Vim). > > I'm not sure I want to support the crazy guys, there's probably lots > of ways to create problems with other events too if that's your goal. > Anyway, what do you have in mind? The current patch is very simple and > I kinda like it to be that way, but if there are obvious stuffs I can > disable/disallow I'll do it.
Using textlock probably works. The problem is that there will always be people that install an autocommand (or use a plugin that has this autocommand without them knowning) and then run into trouble because of unexpected things. It's better to protect the user from destroying his text. Crashing Vim is obviously worse. > > Don't you need to let the commands know what register text was yanked > > into? > > No because every delete/yank use the " register even if a register was > explicitely specified. As a matter of completeness maybe it'd be nice > to know which register was intended yes but it's the first time I > fiddle with vim's source (with some pain) so I'm not too sure how much > work is involved in creating one of those v:somevar. OK, we can add it later when really needed. -- hundred-and-one symptoms of being an internet addict: 101. U can read htis w/o ny porblm and cant figur eout Y its evn listd. /// 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
