Changes: Debugging window autocommands

Revision as of 05:22, 29 September 2008

Please review this tip:

This tip was imported from vim.org and needs general review.
You might clean up comments or merge similar tips.
Add suitable categories so people can find the tip.
Please avoid the discussion page (use the Comments section below for notes).
If the tip contains good advice for current Vim, remove the {{review}} line.

Tip 202 Printable Monobook Previous Next

created January 21, 2002 · complexity advanced · author Hari Krishna Dara · version 6.0

Don't know how people debug autocommands, but I just found out that you can debug (at least) those that result due to window close by just doing a debug quit, i.e.,

:debug quit

Vim will let you step into the autocommands. Try it to believe.

Comments

While going through the help pages, I figured this feature is documented with the following example:

:debug edit <file>

This should let you debug autocommands that get triggered by loading a new buffer.

There's also the :verbose command, with which you can specify the verbosity level for one command only:

:9verbose edit somefile.txt.gz

The verbose levels are documented in :help 'verbose'. The 'verbose' option variable sets verbosity permamently, not just for one command only.

@@ Line 19: / Line 19: @@
 ==Comments==
 While going through the help pages, I figured this feature is documented with the following example:
- :debug edit &lt;file&gt;
+ :debug edit <file>
 This should let you debug autocommands that get triggered by loading a new buffer.