diff options
| -rw-r--r-- | README.md | 4 | ||||
| -rw-r--r-- | TODO.md | 4 |
2 files changed, 5 insertions, 3 deletions
@@ -150,6 +150,10 @@ In my case the solution was to move most of the tags from `/usr/include/` over t Once you've executed the above command, Vim will automatically look for a file named `.tags` in the directory of the current file. Because of the `;` Vim also recurses upwards so that you can nest files arbitrarily deep under your project directories. +### The plug-in doesn't seem to work in [Cygwin](http://en.wikipedia.org/wiki/Cygwin) + +If you want to use the plug-in with Vim under Cygwin, you need to have the Cygwin version of Ctags installed instead of the Windows version (thanks to Alex Zuroff for reporting this!). + ## Contact If you have questions, bug reports, suggestions, etc. the author can be contacted at <peter@peterodding.com>. The latest version is available at <http://peterodding.com/code/vim/easytags/> and <http://github.com/xolox/vim-easytags>. If you like this plug-in please vote for it on [Vim Online](http://www.vim.org/scripts/script.php?script_id=3114). @@ -1,9 +1,7 @@ -# Long term plans +# Long term plans for the easytags Vim plug-in * Automatically index C headers when /usr/include/$name.h exists? - * It seems that Exuberant Ctags doesn't support Objective-C which makes the file type mapping between C and Objective-C useless. Maybe the plug-in should just treat Objective-C source code as C? - * Integration with my unreleased project plug-in so that when you edit any file in a project, all related files are automatically scanned for tags? * Use separate tags files for each language stored in ~/.vim/tags/ to increase performance because a single, global tags file quickly grows to a megabyte? |