huge tags.temp file created in some project in windows about vim-gutentags HOT 9 CLOSED

I'm on Windows 8 with ctags 5.8 but I don't have this problem. Are you using gVim or neovim for this? (I have never tried gutentags on neovim).

To troubleshoot this, pull the latest version of gutentags, and add this to your vimrc:

let g:gutentags_define_advanced_commands = 1

Restart Vim and run :GutentagsToggleTrace. It should tell you that tracing is enabled. Now open a file from that project and you should see some debug output about what command line is being run to generate the tags. You should also see the path for a log file that you can check for more info.

This should give you the exact way ctags is being run, and you can run it by hand and see if for some reason it gets in an infinite loop or something that makes it generate a super huge tags file.
(and actually before you do any of this, you could also just run a vanilla ctags -R inside that project and see if it happens...)

from vim-gutentags.

plain ctags -R is the issue, tags file grows rapidly. Not sure if this should be reported somewhere? I thing ctags in windows is not really updated, ctags5.8 was quite old...

from vim-gutentags.

Are you using plain old ctags, or exhuberant ctags? I just downloaded exhuberant ctags and ran it on that same repository on Windows 8 and it worked fine... I doubt that the Windows version difference between 7 and 8 is the issue here but you never know... either way, it might be good to re-download exhuberant ctags just to make sure?

from vim-gutentags.

Reporting bugs is apparently done here (http://sourceforge.net/p/ctags/bugs/) but judging from the date of the last release and the age of the bug reports in there I'm not sure how that will go :(

from vim-gutentags.

https://github.com/fishman/ctags has been seeing a lot of attention, might want to file a bug there (or maybe it's already fixed)

from vim-gutentags.

@ludovicchabant yes, I am using exhuberant ctags from sf. My suspicion is that you did not reproduce it not because vin7/win8 diff, but because you have less source code. If you just clone the neovim.AS repo, you have just its own source, but if you do this:

npm install -g grunt-cli
path_to_Atom\resources\app\apm\bin\apm.cmd install .
grunt

this will bring a number of deps (in the form of js souce), that then possible create the issue. You need the following installed for this:

nodeJS
Atom

@justinmk I didn't know about that fork, have they produced any release newer than ctags5.8? could not find a windows binary

from vim-gutentags.

Ah yeah I have stuff like node_modules in my default exclude list in my .ctags file.

from vim-gutentags.

ok, I verified

ctags -R --exclude=node_modules

does not have the issue. I also added node_modules to my g:gutentags_exclude and now the issue is gone.
thanks!

from vim-gutentags.

Note that you can add some global excludes to a ~/.ctags or to g:gutentags_exclude (depending on whether you want it to happen always, even when running ctags yourself, or just always in gutentags), but if you want to exclude stuff only for that specific project, you can create a .ctags file at that project's root, and add the exclude rules in there. This may be useful if you want other projects to have their node_modules indexed.

from vim-gutentags.