-
Notifications
You must be signed in to change notification settings - Fork 619
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
Incorrect file path in counsel-etags-find-tag-at-point
#697
Comments
Run |
There're no errors. Also, I've been ran into emacs coredump occasionally when I was using Just FYI, some of the classes/functions are compiled in separate |
Yes, you should exclude I use Emacs Lisp to parse the text. The Emacs Lisp can't handle long lines (say 10000). This is a known problem of Emacs for ages. |
Thanks! I'll give them a try a.s.a.p! |
Confirmed that emacs coredump issue is not reoccuring (at least for the short period I tried), however, the incorrect path issue still exists. Even if I regenerate the tags files. BTW, is the tags file generated by ctags usable by vim? I can try that to check if it's due to incorrect tag file. |
Try to give me more details on incorrect path. Or else I can't debug. tags file could only be used by Emacs. |
Was busy shopping last night... Will provide more detail in the weekend... Sorry :( |
I've managed to reproduce the issue with opencv. Here's the procedure:
|
I can't reproduce the bug. Try to update with latest Maybe it's ctags problem? Could you double check content of TAGS? Is path correct in that file? My ctags version is |
That's really strange. I just checked the TAGS file, the path in that file is not correct:
I am using Exuberant ctags versioned 5.8.5 from ArchLinux original repo, which points to https://www.archlinux.org/packages/extra/x86_64/ctags/
I'd like to try with your version of 5.9 Exuberant Ctags, can you paste me the link to it? Thanks. BTW, updating |
I use ctags from debian testing. Looks it's ctags problem. You can use unverisal ctags instead. |
Thanks. After switching to universal ctags, there're no such issues now. Perhaps you may update README to record this issue. |
I was trying your configs for C++ code navigation, however, I ran into issues when Emacs incorrectly jump to a file which does not exist at all.
Sometimes, there was missing one or more letters in the path prompt, sometimes there're duplicates chars in the path, in any case the selected path pointed to nothing in my file system and Emacs was complaining the following messages. However, sometimes, the path is correct and Emacs can jump to the correct location.
BTW, I was using Ctags as the backend for navigation, I'm not sure whether this is a bug of
counsel-etags
or Ctags itself.I'll provide more examples later with navigating open source code.
The text was updated successfully, but these errors were encountered: