Re: Bad moves with xref-find-definitions

[Vitalie Spinu <spinuvit@gmail.com>]

 >>> Dmitry Gutov on Sun, 26 Apr 2015 18:09:19 +0300 wrote:

 > On 04/26/2015 01:44 PM, Vitalie Spinu wrote:
 >> Me too.

 > But you're willing to prepend `M-3' every time you want to look up something in
 > Elisp? That's not really ideal either.

Not ideal but at least it's context free. And you don't need it that
often from other places anyways.

 > Personally, I expect "serious" backends to either replace the need for etags
 > entirely, or delegate to them and collect the results internally.

It's not really possible. Sometimes you just need to open related
project without "sourcing" it or an old version of the current project
to keep it as a reference. No "serious" backend can accommodate that.

Besides etags it might be potentially handy to have multiple backends
within a mode. In clojure for example you can have one backend for pure
clojure code and another for java code. If xref is able to merge
backends and provide a nice UI to manage those backends then CIDER would
not need to bother with merging or managing those.

As this and other threads suggest managing backends is a non-trivial
task. If you leave this task to major modes everyone will cook his own
soup resulting in a variety of different interfaces.

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

 > Added.

Thanks!

  Vitalie