Mercurial > vim-gutentags
comparison doc/gutentags.txt @ 85:0424970d81f8
Add a `g:gutentags_resolve_symlinks` option to resolve symlinks at setup time.
author | Ludovic Chabant <ludovic@chabant.com> |
---|---|
date | Fri, 09 Oct 2015 15:28:39 -0700 |
parents | cb1cf815052e |
children | 073e63cc0456 |
comparison
equal
deleted
inserted
replaced
84:96bfe5c37f37 | 85:0424970d81f8 |
---|---|
327 Specifies a directory in which to create all the tags | 327 Specifies a directory in which to create all the tags |
328 files, instead of writing them at the root of each | 328 files, instead of writing them at the root of each |
329 project. This is handy to keep tags files from | 329 project. This is handy to keep tags files from |
330 polluting many directories all across your computer. | 330 polluting many directories all across your computer. |
331 | 331 |
332 *gutentags_resolve_symlinks* | |
333 g:gutentags_resolve_symlinks | |
334 When set to 1, Gutentags will resolve any symlinks in | |
335 the current buffer's path in order to find the project | |
336 it belongs to. This is what you want if you're editing | |
337 a symlink located outside of the project, and it | |
338 points to a file inside the project. However, this is | |
339 maybe not what you want if the symlink itself is | |
340 part of the project. | |
341 Defaults to 0. | |
342 | |
332 *gutentags_define_advanced_commands* | 343 *gutentags_define_advanced_commands* |
333 g:gutentags_define_advanced_commands | 344 g:gutentags_define_advanced_commands |
334 Defines some advanced commands like | 345 Defines some advanced commands like |
335 |GutentagsToggleEnabled| and |GutentagsUnlock|. | 346 |GutentagsToggleEnabled| and |GutentagsUnlock|. |
336 | 347 |