|
From: | Dmitry Gutov |
Subject: | bug#19466: 25.0.50; xref-find-def doesn't find C functions |
Date: | Mon, 05 Jan 2015 02:14:23 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Thunderbird/33.0 |
On 01/04/2015 11:29 PM, Eli Zaretskii wrote:
Btw, I think I've found another "issue" with xref-find-def: it uses the TAGS table information without any tolerance. So if you have a TAGS file that is slightly outdated, you are put on the wrong line. By contrast, etags.el had special code that would look around the position specified by TAGS, see etags-goto-tag-location.
I see. Sounds like a good reason to add a yet-another xref-location subclass.
And one more thing: after invoking M-. and typing the function name, then typing '.' to get the first candidate displayed, if I switch to the window where that candidate is displayed, the window switches buffers on me, so that the function I wanted to look at disappears. What am I doing wrong this time?
You didn't press RET after `.'? :)Currently, pre-command-hook always restores window configuration to the one before the buffer with the definitions of the current line's xref was displayed.
I can see how this can be surprising for a new user, though. In that respect, a `quit-window' approach is better.
[Prev in Thread] | Current Thread | [Next in Thread] |