Closed obxhdx closed 12 years ago
Holy crap, it grows to >= 150 MB on the first run?! The only way I can imagine this happening is if you're using the autorecurse option. If you are, I suggest to reconsider whether you really want to have that option enabled :-). If you don't have this option enabled then this is definitely a bug, but I would be surprised if either Exuberant Ctags or the vim-easytags plug-in has such a huge issue without lots more complaints.
Epic tags file
Yep, it grows that large on the very first run. And yes, I'm using the autorecurse option. I actually use autocmd to enable this option only for certain filetypes. So it seems, I can't use it for javascript files at all :(. Isn't there a way to make it ignore some folders while scanning the file system?
Isn't there a way to make it ignore some folders while scanning the file system?
Yes there is. The documentation explains how to pass custom command line arguments to Exuberant Ctags. This means you can add the following lines to your ~/.ctags
file (use the %USERPROFILE%\ctags.cnf
file if you're on Windows):
--exclude=/home/obxhdx/.rvm
--exclude=/home/obxhdx/Music
Hope this helps!
A bit late but... that did the trick, thank you!
maybe you can try "--sort=foldcase" this option of ctags.
My *.js tags file grows absurdely huge the very first time I open any javascript file. I have g:easytags_by_filetype setted, but it doen's make a difference in this case, as my js tags file always end up with about 172mb size.
I took a look at the tags file and it has entries from many hidden directories like the .rvm folder and even from my music folder. I also tried to ignore some paths using the wildignore setting, but it didn't work.
Is there a way to prevent the file from growing so large?