Mercurial > vim-gutentags

comparison doc/gutentags.txt @ 244:d3f9a92399d1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Separate the default project marker finder into a function. This lets people who write custom marker finders fallback to the default behaviour if needed.
author Ludovic Chabant <ludovic@chabant.com>
date Wed, 13 Mar 2019 21:56:19 -0700
parents 050d0549ecf3
children 57654e0dea1c
comparison
equal deleted inserted replaced
243:050d0549ecf3 244:d3f9a92399d1
382 `vim-projectroot`. The value of this setting must be 382 `vim-projectroot`. The value of this setting must be
383 the name of a function that takes a single string 383 the name of a function that takes a single string
384 argument (the path to the current buffer's file) and 384 argument (the path to the current buffer's file) and
385 returns a string value (the project's root directory). 385 returns a string value (the project's root directory).
386 Defaults to `''`. 386 Defaults to `''`.
387 Note: when set, the called implementation will most 387 Note: when set, the called implementation will
388 likely ignore |g:gutentags_project_root|. 388 possibly ignore |g:gutentags_project_root|.
389 Note: an implementation can fallback to the default
390 behaviour by calling
391 `gutentags#default_get_project_root`.
389 392
390 *gutentags_generate_on_missing* 393 *gutentags_generate_on_missing*
391 g:gutentags_generate_on_missing 394 g:gutentags_generate_on_missing
392 If set to 1, Gutentags will start generating an initial 395 If set to 1, Gutentags will start generating an initial
393 tag file if a file is open in a project where no tags 396 tag file if a file is open in a project where no tags