New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ctags job failed, returned: 1 #169
Comments
I encounter the same thing, anything we can do to help? |
@jhogendorn, @aquatix What is the output of trace? |
Maybe related to #177? |
Interesting find, but I don't have a list_command specified in my vimrc. Only config I have is the following (using Vundle):
|
@aquatix, Do you have ctags-exuberant installed on your system? |
Yes, that's the ctags version I'm using. Will try to get a trace. |
I have been getting this issue as well... |
So, is this issue still exist?
|
Same problem here. I'm using the plugin in its default configuration. Trace output right after saving a file (in a latex project) is:
I've executed the script with the parameters given by the trace and it stops with an error message: ctags: "tags.temp" doesn't look like a tag file; I refuse to overwrite it. And indeed, looking in the tag file, the first three lines are clobbered with some artifacts from the files in the project:
After that the file looks rather normal. I'll have a deeper look on how this happens this evening. |
So I checked a bit more in detail. At least in my case, the problem seems to be caused by exuberant-ctags, not by gutentags. If I run a ctags -R . in the directory in question manually, without vim or gutentags running. I can reproduce this issue on this single source directory, but not on others, furthermore it seems only to be an issue on my Ubuntu machine at work, but not on my Fedora machine at home. I'll check that in detail and report upstream if necessary. @jhogendorn, @aquatix could you check, if in your case the error is also caused by a similar corrupted tag file? |
It looks like a corrupted file here too indeed, there's 52 lines of cruft before the line with !_TAG_FILE_FORMAT In my case, it was cause by some TeX file(s) that were followed from a symlink to another directory outside the 'project root'. After removing that link, ctags creates a valid file again. |
Wow that's pretty random :) Thanks for investigating. I guess we should find a way to better report that the |
Just in case anyone cares, this sort of issue with ctags was reported 6 years ago and is still open https://sourceforge.net/p/ctags/bugs/332/ there is a similar ticket for some javascript. Seems there is no active development on ctags for some time now. @ludovicchabant The message would be good to have (or in general a more verbose error message, if the job fails), at least as option. |
@ludovicchabant yeah, having the ctags messages bubble up, would help, as it's way more clear for the user that it's something that's bugging ctags, not vim-gutentags. @d3rhans OK, that's slightly bad indeed. I hope someone feels irked enough to take up active development again (no, I won't take another pet project ;)). Thanks all for investigating, would not have found the solution so easily without the various pointers. |
I have the same problem.
114 let g:gutentags_project_root = ['.git', '.svn', '.root', '.hg', '.project']
115 let g:gutentags_ctags_tagfile = '.tags'
116 let s:vim_tags = expand('~/.cache/tags')
117 let g:gutentags_cache_dir = s:vim_tags
118 let g:gutentags_ctags_extra_args = ['--fields=+niazS', '--extra=+q', '--c++-kinds=+px', '--c-kinds=+px']
119 let g:gutentags_trace = 1
120 let g:gutentags_file_list_command = {
121 \ 'markers': {
122 \ '.git': 'git ls-files',
123 \ '.hg': 'hg files',
124 \ }
125 \ }
BTW, I'm using |
Just found that the command being run is something like:
The problem there is
Seems it runs ctags like:
But on the ctags man page, it specifies that
There is no rest of the string after the |
Yep, sorry, I introduced that bug with a change yesterday -- you most likely get this bug if your |
@ludovicchabant Unfortunately I still have this bug with the latest version of the plugin |
Here are what my log output:gutentags: gutentags: ctags job failed, returned: 1 |
Notice how it says |
Hi there, was it already patched?
When it get fix will it be on master. |
Got this in MacOS too. I think it's because the system ctags was in my path before exuberant ctags from homebrew. |
I had no ctags installed at all on one of my machines on MacOS. And I got the same error. |
I've tried to remove execution as @sagotsky said. But probably the macos system protection don't allow to change it. So as I nottice that my problems was about vim not calling a compatible ctags (exuberant or universal), I'v tried to re-install and relink with brew, almost the same as @snipem suggested, but with no sucess to me. So my sollution what to add this line on my vimrc
this variable is on gutentags documentation. So I just placed the fullpath to ctags that I want it to run. Hope to help others. PS: If I've written something wrong please tell me, so I may learn and correct, as english is not my first language. |
@snipem : in theory, Gutentags checks for the case where @wviana to make it slightly prettier, and handle the case where you'll run |
I'm gettting
@ludovicchabant What should I do. |
I'm getting this error when ctags outputs some warning about files or directories it is not able to open or parse. Everything else seems to work though. Could it be that ctags just returns non-zero if there is some warning, even though everything is fairly ok? |
Tag generation is also failing for me. The error message boils down to:
The weird part is that this folder - whatever it is and wherever a reference to it is coming from - seems to be passed in as something to exclude. I.e. ctags is told to exclude this folder, but then it generates an error saying it can't open it, which doesn't seem to make a lot of sense. Full message:
After a reboot, all seems well again...still a rather strange issue. |
I reinstalled I ended up uninstalling I do not need to set the |
I'm using https://github.com/universal-ctags/homebrew-universal-ctags and ran into this issue. At some point the brew symlinks went missing, or were never installed. This fixed it for me
|
gutentags: Wildignore options file is up to date. i get this error but only on my dotfiles repo |
LOL nvm. i had some unintended config |
(For posterity) if you are using FreeBSD, doing ln -s /usr/local/bin/exctags /usr/bin/ctags |
Hi
Here is my fail logs:
|
Hi, maybe late to the party. I am on OpenBSD 7.3. |
I'm getting the above message on BufWrite. A tag file is getting generated. I've tried running with
let g:gutentags_trace = 1
but thats not giving me any useful error message as to why ctags might be failing.What steps can I take to debug this?
The text was updated successfully, but these errors were encountered: