Set nocscopetag doesn't work?

[jiji879]

For example 1tag xxxx always jump to itself if contains the same definition, details see in last comment of #58 .

[complex857]

Please excuse my ignorance, but could you expand on what seems to be problem?
I've read comment in #58, however those numbers are not chosen by random but by trying to match the file associated on the returned list with the searched symbol's file (this piece of info is from phpcomplete#LocateSymbol).

I believe the #58 was there because with the cscopetags enabled the :tag command was ignoring the leading [count] in there.
The fact the same prefix number means different tags for invocation to invocation in itself isn't a bug or issue as far as i understand - please correct me if I'm wrong here.

[jiji879]

Thx. you know exactly what i mean. but doesn't set nocscopetag turn it off?

i understand that the fixed tag_position will be found in same symbol right? but if a invocation be found in first of the tags: 1tag xxx, it always jump to itself but not the actually definition.

it seems like that jump is relative to tag of current file. i had tried set nocst or set csto=1 but doesn't work.

[complex857]

Yes, as far as I know it does. I'm sorry, but I think I'm still at lost on what is broken exactly.

The tag_position number is always re-calculated for every invocation of the plugin. So the numbers we gonna stick in front of the tag <symbol> commands should always be recalculated. I don't think the 1tag ... will always be "itself" the symbol you are on might not even be on the taglist. The ordering of the list should be done according tag-priority. So if there's a symbol you are trying to jump is in the same file as a tag and the plugin thinks that in the current context (based on for example the guessed type of the variable in front of the tag if it's a method invocation or such) then yes, otherwise it will jump without a number and let the tag-priority decide (as if the plugin wasn't installed).

I'm still at lost on if you have some "This is what I do, This is what I expect to happen, This happens instead" kinda bug we can try to fix, if you could phrase your issue that way it would help me out a lot!