Mercurial > vim-gutentags
comparison doc/gutentags.txt @ 142:d4c09aa41e80
Typo
author | nblock <nblock@users.noreply.github.com> |
---|---|
date | Thu, 27 Oct 2016 13:11:25 +0200 |
parents | 95092f4fbc4b |
children | 513bcd0a1f90 8a93fca41a38 |
comparison
equal
deleted
inserted
replaced
140:95092f4fbc4b | 142:d4c09aa41e80 |
---|---|
106 | 106 |
107 *gutentags-project-commands* | 107 *gutentags-project-commands* |
108 The following commands are only available in buffers that have been found to | 108 The following commands are only available in buffers that have been found to |
109 belong to a project that should be managed by Gutentags. See | 109 belong to a project that should be managed by Gutentags. See |
110 |gutentags_project_root| for how Gutentags figures out the project a file | 110 |gutentags_project_root| for how Gutentags figures out the project a file |
111 belongs to. When not project is found (i.e. the file is not under any of the | 111 belongs to. When no project is found (i.e. the file is not under any of the |
112 known project markers), Gutentags is disabled for that buffer, and the | 112 known project markers), Gutentags is disabled for that buffer, and the |
113 following commands and remarks don't apply. | 113 following commands and remarks don't apply. |
114 | 114 |
115 If you want to force-disable Gutentags for a given project even though it does | 115 If you want to force-disable Gutentags for a given project even though it does |
116 match one of the items in |gutentags_project_root|, create a file named | 116 match one of the items in |gutentags_project_root|, create a file named |