Indexing updated source truncates tag file about vim-gutentags HOT 6 CLOSED

Found that grep was failing as it detected the tags file as binary. I still don't know why this is happening but adding the -a switch forces grep to treat the file as text, which resolves the issue.

from vim-gutentags.

Ah interesting. My guess is that maybe ctags is somehow indexing binary files, or source files with "unusual" character sets, so the tags file ends up with some symbols that contain characters that it interprets as binary? However, I'm worried that using the -a switch messes up Unicode symbols... it's pretty unusual (most programming languages are ASCII only) but it can happen.

from vim-gutentags.

Ok I just merged a PR which adds the --text flag, which is the same a -a. Thanks!

from vim-gutentags.

Updating tag file still truncates it for my even with grep --text command. What can be the issue?

from vim-gutentags.

No idea off the top of my head... :(

If you enable tracing (:call gutentags#toggletrace()) you will get a log file next to your tags file which shows what happened. This way you can run every step by hand in the command line and see at what point the tags file got truncated...

from vim-gutentags.

Sorry, there was a problem with my ctags. Your plugin works smooth.

On Aug 10, 2016 6:54 AM, "Ludovic Chabant" [email protected] wrote:

No idea off the top of my head... :(

If you enable tracing (:call gutentags#toggletrace()) you will get a log
file next to your tags file which shows what happened. This way you can run
every step by hand in the command line and see at what point the tags file
got truncated...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#81 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJtpYm7FE-SYx5EQEsTMrgYLzj-PIj4Bks5qeUt6gaJpZM4IFsKW
.

from vim-gutentags.