Mercurial > vim-gutentags
changeset 129:48045d81f25a
Fix some typos in the docs.
| author | Ludovic Chabant <ludovic@chabant.com> |
|---|---|
| date | Tue, 19 Jul 2016 23:30:15 +0200 |
| parents | e673026faa56 |
| children | b6ec4caa22ff |
| files | doc/gutentags.txt |
| diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/gutentags.txt Mon Jun 13 19:25:52 2016 -0700 +++ b/doc/gutentags.txt Tue Jul 19 23:30:15 2016 +0200 @@ -54,12 +54,12 @@ time you save, it will silently, in the background, update the tags for that file. -Usually, ctags can only append tags to an existing tag file, so Gutentags +Usually, `ctags` can only append tags to an existing tag file, so Gutentags removes the tags for the current file first, to make sure the tag file is always consistent with the source code. Also, Gutentags is clever enough to not stumble upon itself by triggering -multiple ctags processes if you save files to fast, or your project is really +multiple ctags processes if you save files too fast, or your project is really big. There are some similar Vim plugins out there ("vim-tags", "vim-autotag", @@ -76,8 +76,8 @@ the tag file, otherwise you will still "see" tags for deleted or renamed classes and functions. * Automatically create the tag file: you open something from a freshly forked - project, it should start indexing it automatically, just in Sublime Text or - Visual Studio or any other IDE. + project, it should start indexing it automatically, just like in Sublime Text + or Visual Studio or any other IDE. =============================================================================