On 2017-01-24, Bram Moolenaar wrote: > Gary Johnson wrote: > > > On 2017-01-24, Christian Brabandt wrote: > > > Hi Bram! > > > > > > On Di, 24 Jan 2017, Bram Moolenaar wrote: > > > > > > > Hmm, so when using "eventignore=all" perhaps the TermResponse should not > > > > be ignored? Or should we support the value "all,-TermResponse"? > > > > It's going to be tricky either way. > > > > > > I think it should not be ignored. If one really wants to ignore it, one > > > could set t_RV to an empty string. > > > > I don't think setting t_RV to an empty string will fix the problem. > > If netrw wants to ignore the termresponse from the terminal, I think > > setting t_RV to an empty string will be too late. I think Vim has > > already sent t_RV when netrw is invoked. Also, triggering > > a TermResponse autocommand is different from setting v:termresponse, > > which is done even if TermResponse is ignored. > > A better solution would be that the TermResponse event is postponed > until 'eventignore' has been reset. Since it is unrelated to the > current state of Vim (buffer, window, etc.) that should be OK.
I was thinking of that, too. Postponing it also has the benefit that if the response to the TermResponse event is to do something that would generate another autocommand event, such as changing the color scheme, those other events would not be unexpectedly ignored. Regards, Gary -- -- 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.
