Thursday, August 17, 2017

Re: does VIM read OK the tags file if ctags was installed after VIM?

2017-08-15 17:44 GMT-04:00 Benji Fisher <benji17fisher@gmail.com>:
> On Tue, Aug 15, 2017 at 4:42 PM, Jose Caballero <jcaballero.hep@gmail.com>
> wrote:
>>
>> Thanks Ben and Erik.
>>
>> Both tags files are identical:
>>
>> host1 $ md5sum tags
>> 34e5413f4dea1c0644b35de7808a8029 tags
>>
>> host2 $ mad5sum tags
>> 34e5413f4dea1c0644b35de7808a8029 tags
>>
>> Also tags are equal:
>>
>> :set tags?
>> tags=./tags,./TAGS,tags,TAGS
>>
>>
>> But, when hitting CTRL+] on top of a tag....
>>
>> @ host1 I get the expected
>>
>> # pri kind tag file
>> 1 F C i StatusInterface plugins/status/Plugin.py
>> from interfaces import StatusInterface
>> 2 F c StatusInterface interfaces.py
>> class StatusInterface(object):
>>
>>
>> @ host 2, I get something like "tag 1 of 2 or more", and that's it.
>>
>> Both host have VIM 7.4.160
>>
>> Huh?
>>
>> Cheers,
>> Jose
>
>
> That seems odd. I think that my first suggestions would have been the same
> as Ben and Erik's.
>
> Does :ts help clarify the situation?
>


hmmm.
That is interesting.
In both cases, after trying a tag, :ts gives me the same, similar to

# pri kind tag file
1 F C i StatusInterface plugins/status/Plugin.py
from interfaces import StatusInterface
2 F c StatusInterface interfaces.py
class StatusInterface(object):

And, indeed, typing the number opens the right file, as it was
supposed to work with CTRL+]

It is like the actual command CTRL+] is the one that is not working in
one of the hosts, but the tags information has been read by VIM and
it's reachable via :ts

Cheers,
Jose

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: