Mercurial > vim-gutentags
comparison doc/gutentags.txt @ 182:2489b4b54d5c
Add `g:gutentags_generate_on_empty_buffer` setting.
| author | Ludovic Chabant <ludovic@chabant.com> |
|---|---|
| date | Tue, 18 Apr 2017 21:43:59 -0700 |
| parents | cbc1ebe23ef1 |
| children | 676fe2ea919f |
comparison
equal
deleted
inserted
replaced
| 181:0b4ccd0deceb | 182:2489b4b54d5c |
|---|---|
| 379 This means that the project's tag file won't reflect | 379 This means that the project's tag file won't reflect |
| 380 the latest changes, and you will have to run | 380 the latest changes, and you will have to run |
| 381 |GutentagsUpdate| manually. | 381 |GutentagsUpdate| manually. |
| 382 Defaults to 1. | 382 Defaults to 1. |
| 383 | 383 |
| 384 *gutentags_generate_on_empty_buffer* | |
| 385 g:gutentags_generate_on_empty_buffer | |
| 386 If set to 1, Gutentags will start generating the tag | |
| 387 file even if there's no buffer currently open, as long | |
| 388 as the current working directory (as returned by | |
| 389 |:cd|) is inside a known project. | |
| 390 This is useful if you want Gutentags to generate the | |
| 391 tag file right after opening Vim. | |
| 392 Defaults to 0. | |
| 393 | |
| 384 *gutentags_background_update* | 394 *gutentags_background_update* |
| 385 g:gutentags_background_update | 395 g:gutentags_background_update |
| 386 Specifies whether the process that updates the tags | 396 Specifies whether the process that updates the tags |
| 387 file should be run in the background or in the | 397 file should be run in the background or in the |
| 388 foreground. If run in the foreground, Vim will block | 398 foreground. If run in the foreground, Vim will block |