Luc Hermitte (talk | contribs) m (Added to Scripting category) |
(adjust previous/next navigation + minor manual clean) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{review}} |
{{review}} |
||
| + | {{TipImported |
||
| − | {{Tip |
||
|id=202 |
|id=202 |
||
| + | |previous=199 |
||
| − | |title=debugging window autocommands |
||
| + | |next=203 |
||
| − | |created= |
+ | |created=2002 |
|complexity=advanced |
|complexity=advanced |
||
|author=Hari Krishna Dara |
|author=Hari Krishna Dara |
||
|version=6.0 |
|version=6.0 |
||
|rating=17/5 |
|rating=17/5 |
||
| ⚫ | |||
| − | |text= |
||
| + | |category2= |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
Vim will let you step into the autocommands. Try it to believe. |
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: |
+ | While going through the help pages, I figured this feature is documented with the following example: |
| − | :debug edit |
+ | :debug edit <file> |
| − | This should let you debug autocommands that get triggered by loading a new buffer. |
+ | This should let you debug autocommands that get triggered by loading a new buffer. |
| − | Hari |
||
| − | |||
| − | hari_vim at yahoo.com |
||
| − | , January 21, 2002 19:04 |
||
---- |
---- |
||
| − | There's also the :verbose command, with which you can specify the verbosity level for one command only: |
+ | There's also the :verbose command, with which you can specify the verbosity level for one command only: |
| − | :9verbose edit somefile.txt.gz |
+ | :9verbose edit somefile.txt.gz |
| − | The |
+ | The verbose levels are documented in {{help|'verbose'}}. The 'verbose' option variable sets verbosity permamently, not just for one command only. |
| − | (The 'verbose' option variable sets verbosity permamently, not just for one command only) |
||
| − | Mark Hillebrand |
||
| − | , February 19, 2002 6:31 |
||
---- |
---- |
||
| − | <!-- parsed by vimtips.py in 0.590702 seconds--> |
||
| − | |||
| ⚫ | |||
Latest revision as of 08:53, 22 January 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.
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.