On 09/02/2016 09:51 PM, LCD 47 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?

I use the QuickFixCmdPre/Post to automatically open / adapt the size of
/ close the quickfix window, and therefore appreciate that all
quickfix-manipulating commands are covered.

The fix of Syntastic should be pretty easy, as one can use the autocmd
pattern to exclude [cl]getexpr, right?

-- regards, ingo

-- 
-- 
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.

Attachment: signature.asc
Description: OpenPGP digital signature

Raspunde prin e-mail lui