On Tuesday, January 15, 2013 1:51:05 PM UTC-6, ZyX wrote: > > 'eventignore' also confuses me. Although it makes sense that it could cause > > problems, ignoring it would be a very bad idea, it's only ever set by the > > user for a specific purpose. > > > > Wondering what purposes may make user set this option? From my experience it > is set by plugins for temporary disabling some things and can easily be > skipped to restore by interrupting: GLVS, netrw (:noautocmd in some cases > would be better) (but it launches commands which result in much less > calculations — and much less possibility to interrupt; except for one place), > tar.vim (same about :noautocmd in some cases), vimball.vim, zip.vim. Exactly > none of them bothered with using :try…:finally, there will be more if I > examine ~/.vam (folder with plugins installed by VAM) in place of > /usr/share/vim.
Yes, you're right, I see it used by user scripts or plugins which need to make changes to buffers quickly without triggering potentially slow autocmds which are not needed for the new buffer. While you're correct that doing so leaves the possibility of the script or plugin accidentally leaving 'eventignore' at a bad value, it's worse in my opinion to ignore the 'eventignore' setting and just run a plugin's events anyway, if a plugin function triggers an autocmd event. How frustrating would it be, to set 'eventignore' to BufRead, to prevent Vim from doing any processing on a buffer you intend to throw away anyway, only to have another plugin ignore your settings and do a bunch of stuff on the read anyway? -- 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
