On Thu, Feb 04, 2016 at 10:04:44PM +0100, Christian Brabandt wrote:
> On Do, 04 Feb 2016, Anton Lindqvist wrote:
>
> > On Thu, Feb 04, 2016 at 09:36:21PM +0100, Christian Brabandt wrote:
> > > While I agree that this is useful, I have been thinking, if a more
> > > general approach would not be more useful. Something like an Error
> > > autocommand, that triggers on the EXXX numbers?
> >
> > I really like this idea, especially if <amatch> would be the actual
> > error message since it would allow people to get creative. Having
> > limited experience with the Vim codebase: would it be feasible to
> > trigger the autocmd event somewhere along the call stack for the emsg
> > functions? At first glance it looks like that solution would require
> > less changes. Compared to adding a explicit call to apply_autocmds
> > prior calling any of the emsg functions.
>
> That's what my half working patch did. It is here:
> https://github.com/chrisbra/vim-mq-patches/blob/master/error_aucmd
> you might want to look into it. Never got around finishing it.
Christian,
I am able to apply your patch and it works fine. Here's an example of a
potential use-case of mine:
" Run ctags if the tag file is missing (E433) or the tag was not found (E426)
augroup ctags
au! Error E4\(26\|33\)* silent exe '!ctags'
augroup END
Are you aware of any bugs with your patch or other potential gotchas that needs
to be resolved?
--
:wq
--
--
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.
