Ludovic Chabant

@RedBug312 Disabling `g:gutentags_generate_on_write` might not do much since it only runs `ctags` on the one file that was written. But disabling some of the other ones (`generate_on_new` and `generate_on_missing`) could...

Has anybody experienced Gutentags making Vim slow or unresponsive recently? It looks like it might have been caused by a combination of plugins and Vim bugs? Also, I could imagine...

Oh nice, I didn't know about `ptags`, thanks for that, I'll give it a try. What didn't work?

Can you do `:call gutentags#toggletrace()` and try again? Then you can do `:messages` and get more info about the failure.

In theory, Neovim is supposed to kill child processes on exit, and the child process' script has a `trap` command in there to clean up files... I wonder why that...

Ah thanks for the link to that comment. That makes sense. I've added Tim's recommended fix to my todo list but obviously if someone wants to take a crack at...

Hi! It's weird that this breaks, as I would expect `ctags` to prioritize command line parameters (`-f` is passed directly) over options from options files... maybe order matters? You could...

@alphaCTzo7G You can try to run `:call gutentags#toggletrace()` to see what Gutentags is doing, and have it leave a log file behind. This way you'll see exactly what command it...

I'm not familiar with gtags but maybe some files had encoding it doesn't handle, or maybe permissions it couldn't access? Either way we should add a `gutentags_gtags_extra_args` so people can...

Do you all have _both_ `ctags` and `gtags_cscope` enabled as Gutentags modules? I'm wondering if the 2 jobs could be messing with each other... can someone try to _only_ enable...