Lcd wrote: > On 1 September 2016, Bram Moolenaar <[email protected]> wrote: > > > > Patch 7.4.2299 > > Problem: QuickFixCmdPre and QuickFixCmdPost autocommands are not always > > triggered. > > Solution: Also trigger on ":expr", ":cbuffer", etc. (Yegappan Lakshmanan) > > Files: src/quickfix.c, src/testdir/test_quickfix.vim > [...] > > Sadly, this breaks the interaction of "syntastic" with all plugins > that hook to QuickFixCmdPre or QuickFixCmdPost. An example of such > plugin is "ferret". These plugins now have to be fixed to be aware that > they may be called from things like :lgetexpr. I'd argue that running > QuickFixCmd* for :lgetexpr makes little sense, since :lgetexpr is almost > never called run interactively. So, was there an actual reason for this > change, right before the release of Vim 8?
Can you give more details about what breaks? The autocommands are there to allow plugins to deal with changes in the Quickfix list. I hope it's not actually being used for something else. -- hundred-and-one symptoms of being an internet addict: 143. You dream in pallettes of 216 websafe colors. /// 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.
