Mercurial > vim-gutentags

comparison doc/gutentags.txt @ 97:794ee111bce6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add documentation for `g:gutentags_ctags_no_space_in_paths`.
author Ludovic Chabant <ludovic@chabant.com>
date Sun, 21 Feb 2016 10:34:47 -0800
parents 54355724204b
children d645125192aa
comparison
equal deleted inserted replaced
96:e03a661dc983 97:794ee111bce6
376 This means, for example, that you can use 376 This means, for example, that you can use
377 `g:gutentags_ctags_executable_ruby` out of the box. 377 `g:gutentags_ctags_executable_ruby` out of the box.
378 See |gutentags_ctags_executable_{filetype}| for more 378 See |gutentags_ctags_executable_{filetype}| for more
379 information. 379 information.
380 380
381 *gutentags_ctags_no_space_in_paths*
382 g:gutentags_ctags_no_space_in_paths
383 When set to 1, the root path of a project will have
384 any spaces replaced by underscores. This is in case
385 the particular `ctags` implementation you're using
386 doesn't support tags filenames with spaces, which
387 seems to be the case with Exuberant Ctags.
388 Set to 0 to leave project root paths as is.
389 Defaults to 1.
390
381 391
382 ============================================================================= 392 =============================================================================
383 5. Project Settings *gutentags-project-settings* 393 5. Project Settings *gutentags-project-settings*
384 394
385 Gutentags can be customized to some extent on a per-project basis with the 395 Gutentags can be customized to some extent on a per-project basis with the