-
Notifications
You must be signed in to change notification settings - Fork 173
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_recursive.options permissions #321
Comments
Looks somehow the process running Vim doesn't have permissions to read one of the files inside the gutentags plugin ( Also, is that newline after the path in the logs, or is that caused by copy/pasting here in Github? I can't see how the code could ever add a newline there. |
Hi @ludovicchabant The last thing I put in the "Additional Context" shows the permissions on that file, because I knew that would be important. As you can see, the persmissions are I am not sure which newline you are talking about, but it is probably a copy paste issue. |
Right, I missed it, thanks. I have no idea why it can't read a |
So, I am opening |
Maybe not relevant, but I get the same error, when using NeoVim as an appimage, which is sandboxed and I suspect the sandboxing to be an issue. I will try a deb install and post my findings here. |
Ok, it seems that I resolved this issue on my machine. I have done the following:
In the end the update_tags script succeeded and I suspect the snap's sandboxing mechanism of messing with reading external files from the general filesystem, but since I did touch 2 things I cannot be 100% certain which of the steps helped. |
Describe the bug
Clean install. When opening any file, ctags throws an error
Steps to reproduce
vim-gutentags
by cloningShare your setup
ctags
,gtags
, or whatever do you have installed?g:gutentags_cache_dir
? Not that I know ofPost the logs
:let g:gutentags_trace = 1
.:messages
and show the messages that Gutentags posted.tags.log
file that Gutentags' script left behind, and post its contents.Additional context
if I try to run the command myself I get the same error from the command line:
As you can see, the permissions on this file are
664
so anything should be able to read itThe text was updated successfully, but these errors were encountered: