diff options
| author | Peter Odding <peter@peterodding.com> | 2011-06-27 03:54:07 +0200 |
|---|---|---|
| committer | Peter Odding <peter@peterodding.com> | 2011-06-27 03:54:07 +0200 |
| commit | 5207365adaf6c62785ab336ec865428155c8e3b6 (patch) | |
| tree | 57af17b0e3e720389da3fbc45e95b6fbc950b3f4 /README.md | |
| parent | 2589d58711419fd61e8561036fd85d50e01dec8a (diff) | |
| download | vim-easytags-5207365adaf6c62785ab336ec865428155c8e3b6.tar.gz | |
Fix broken link in README
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -225,7 +225,7 @@ Every time the plug-in executes it will time how long the execution takes and ad If the `easytags.vim` plug-in fails to highlight your tags and the error message mentions that the pattern is too big, your tags file has grown too large for Vim to be able to highlight all tagged identifiers! I've had this happen to me with 50 KB patterns because I added most of the headers in `/usr/include/` to my tags file. Internally Vim raises the error [E339: Pattern too long] [e339] and unfortunately the only way to avoid this problem once it occurs is to reduce the number of tagged identifiers... -In my case the solution was to move most of the tags from `/usr/include/` over to project specific tags files which are automatically loaded by Vim when I edit files in different projects because I've set the ['tags' option] ['tags'] as follows: +In my case the solution was to move most of the tags from `/usr/include/` over to project specific tags files which are automatically loaded by Vim when I edit files in different projects because I've set the ['tags' option] [tags_opt] as follows: :set tags=./.tags;,~/.vimtags |