-
Notifications
You must be signed in to change notification settings - Fork 175
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
Mixed relative and absolute paths #70
Comments
@gruberjuliannama You seem to have pasted parts of my comment and code from the PR (#71)? |
At commit cbc163f I still have the same problem. When trying to resolve it I used
|
The reason you have duplicate symbols seems to be different, as the 2 paths look the same? |
I do not think it is different because the way to reproduce is the same:
Also without |
FWIW: my issue was fixed with #71 (not merged, because it depends on Python). |
@ZyX-I |
This is something else: file contains exactly one entry, but project root contains |
So let's try to not get confused by various different bugs. The OP was about mixed relative and absolute paths. To be clear, this is what I figured out when I was writing Gutentags:
Gutentags has 2 modes: Unless I'm missing something clever, mode 1 can (and probably should) use relative paths, whereas mode 2 should use absolute paths because the cache directory and project directory are probably totally unrelated. This is why Gutentags passes I believe I fixed the bug @blueyed originally reported with 09fbdfc (I wasn't properly doing that "relative/absolute" switch depending on mode 1 and 2 for single-file updates). The problem is really that I let Gutentags put the |
Hey guys, I want to congratulate you all for all work done so far but I can't get satisfied with it, there are so many bugs. Is there any stable release with a minimum functionality any where? Currently I'm having the same issue, if I enable the cache with:
The duplicate continues to occur but without the mix, all tags remains duplicated with full path. |
I haven't set up branches or labels, no, but you're right, I should probably do that at some point (whenever we can actually identify a "stable" release, really). Since you're using |
Hi @ludovicchabant thanks for you answer. I think that I resolved the problem removing the option cscopetag from my nvimrc and keeping the cache option; |
I had this issue when I had tags generated by a command
And after that I opened a folder I generated ctags for with Vim with this plugin installed and I saw the duplicated tags with absolute and relative paths. Then I quit vim, removed the I am new to Vim (learned about ctags just 2h ago) so it's not a surprise that I did something wrong here. Hopefully my solution will help the other newbies [: |
Disables the detection of tags_file_is_local. Adds an additional way of fixing ludovicchabant#70 , by forcing only absolute paths.
I've noticed that a full update (
GutentagsUpdate!
) would use relative filenames, but a partial update for the current file (GutentagsUpdate
) absolute ones.This causes Vim (Neovim) then to display the tag selection with
:tj
, because the path differs.Can you confirm this?
I am using universal-ctags, and reported the issue there in a pull request, which fixes this when using
--tag-relative=yes
: universal-ctags/ctags#868.Since the code in this area appears to date back to the early days of ctags, I assume that this affects gutentags in general?!
A fix might be to make
UPDATED_SOURCE
local to the tags file?!The text was updated successfully, but these errors were encountered: