Skip to content
Browse files

Added caveat about Cygwin, updated to-do list

  • Loading branch information...
1 parent 98780b1 commit ea6efd67beffd43251f155cf948f400e0333e714 @xolox committed Feb 24, 2011
Showing with 5 additions and 3 deletions.
  1. +4 −0
  2. +1 −3
@@ -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](
+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 <>. The latest version is available at <> and <>. If you like this plug-in please vote for it on [Vim Online](
@@ -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?

0 comments on commit ea6efd6

Please sign in to comment.
Something went wrong with that request. Please try again.