[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bad moves with xref-find-definitions

From: Dmitry Gutov
Subject: Re: Bad moves with xref-find-definitions
Date: Sun, 26 Apr 2015 06:37:25 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Thunderbird/36.0

On 04/25/2015 11:43 PM, Vitalie Spinu wrote:

It probably should be generic such that other "finding" or "jumping"
functionality can reuse it (prompt-before-jump, auto-jump).

Maybe the rule could be whether the command is almost always related to the current buffer's contents.

`describe-function' and friends I would actually consider to be counter-examples, because they only work with Elisp.

And similarly how certain other people are attached to etags, I'd always want to have access to Elisp documentation and sources, even when editing unrelated code in another language.

Hence I think we need a separate, generalizable command and binding that would work with different modes and depend on the current language or project. That one could work like SLIME's `C-c C-d C-d'.

The problem is of course that "find-file" is also a "finding" behavior,
for which you unlikely to want this behavior. So it's difficult to draw
a line on what are these commands.

Let's stop at xref, for now.

More specific name like xref-auto-jump seems quite suggestive to me.

How about `xref-prompt-for-identifier', to mirror CIDER's option name?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]