# HG changeset patch # User Ludovic Chabant # Date 1408652703 25200 # Node ID b13e1141aa5cd72c85d7e0fef31feb7f159fdd64 # Parent b734662688442ba72d784986dd36f8ad3e46876b Fix wording in `README`. diff -r b73466268844 -r b13e1141aa5c README.md --- a/README.md Thu Aug 21 13:24:52 2014 -0700 +++ b/README.md Thu Aug 21 13:25:03 2014 -0700 @@ -50,19 +50,19 @@ * No other dependency than running Vim: no Python, Ruby, or whatever. * Cross-platform: should work on at least Mac and Windows. -* Incremental tags generation: don't re-generate the whole project all the - time. This may be fine for small projects, but it doesn't scale. -* External process management: if the ctags process is taking a long time, - don't run another one because I saved the file again. -* Keep the tag file consistent: don't just append the current file's tags to - the tag file, otherwise you will still "see" tags for deleted or renamed - classes and functions. +* Incremental tags generation: don't re-generate the whole project all the time. + This may be fine for small projects, but it doesn't scale. +* External process management: if the ctags process is taking a long time, don't + run another one because I saved the file again. +* Keep the tag file consistent: don't just append the current file's tags to 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. I hope Autotags will bring you as much closure as me regarding tag files. I know -I don't want to think about it, and probably neither do you. +I don't want to have to think about it, and probably neither do you. [ctrlp]: https://github.com/kien/ctrlp.vim