Wikia

Vim Tips Wiki

Changes: Debugging window autocommands

Edit

Back to page

(Remove html character entities)
(adjust previous/next navigation + minor manual clean)
 
Line 2: Line 2:
 
{{TipImported
 
{{TipImported
 
|id=202
 
|id=202
|previous=201
+
|previous=199
 
|next=203
 
|next=203
|created=January 21, 2002
+
|created=2002
 
|complexity=advanced
 
|complexity=advanced
 
|author=Hari Krishna Dara
 
|author=Hari Krishna Dara

Latest revision as of 08:53, January 22, 2011

Tip 202 Printable Monobook Previous Next

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

CommentsEdit

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.


Around Wikia's network

Random Wiki