Mercurial > vim-gutentags

comparison doc/gutentags.txt @ 123:76a4822aab76

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use existing b:gutentags_root This could be set from g:gutentags_enabled_user_func then, for example.
author Daniel Hahler <git@thequod.de>
date Wed, 06 Apr 2016 18:05:39 +0200
parents d645125192aa
children e2a43c03da79
comparison
equal deleted inserted replaced
117:df3b0ca48013 123:76a4822aab76
330 330
331 *gutentags_enabled_user_func* 331 *gutentags_enabled_user_func*
332 g:gutentags_enabled_user_func 332 g:gutentags_enabled_user_func
333 When set to a non-empty string, it is expected to be 333 When set to a non-empty string, it is expected to be
334 the name of a function that will be called when a file 334 the name of a function that will be called when a file
335 is open in a project. The function gets passed the 335 is opened in a project. The function gets passed the
336 path of the file and if it returns 0, Gutentags won't 336 path of the file and if it returns 0, Gutentags won't
337 be enabled for that file. 337 be enabled for that file.
338 You can use this also to manually set `b:gutentags_root`
339 (see |gutentags_project_root|).
338 Defaults to "". 340 Defaults to "".
339 341
340 *gutentags_define_advanced_commands* 342 *gutentags_define_advanced_commands*
341 g:gutentags_define_advanced_commands 343 g:gutentags_define_advanced_commands
342 Defines some advanced commands like 344 Defines some advanced commands like