Saturday, March 9, 2013

Re: Is there a way to see autocommand events fire?

On Friday, March 8, 2013 2:23:52 PM UTC-6, coot_. wrote:
> On 07:28 Fri 08 Mar , Axel Bender wrote:
>
> > I'm looking for a way to see the order in which autocommand events fire.
>
> > Setting verbose doesn't seem to do...
>
> >
>
> > --
>
> > --
>
> > You received this message from the "vim_use" 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_use" group.
>
> > To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
>
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> >
>
>
>
> I once found a script which did that so you should try to google.
>
> Anyway writing it is as simple as:
>
>
>
> augroup AutoCmdTest
>
> au BufEnter * echom 'BufEnter'
>
> au BufWritePre * echom 'BufWritePre'
>
> au BufWritePost * echom 'BufWritePost'
>
> augroup END
>
>
>
> It is usually enough to investigate a few autocommand groups if reading
>
> ':help autocmd-events-abc' is not enough. Then you can see :mes for the
>
> messages.
>
>
>
> If you want to finish your test just use:
>
>
>
> :augroup AutoCmdTest
>
> :au!
>
> :augroup END
>
>
>
> it should flash all the autocommands in AutoCmdTest group.
>
>
>
> Best regards,
>
> Marcin

Weird, I don't see the original post anywhere.

You can always try the :debug command.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: