unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: Allow xref to use other than current major-mode
Date: Tue, 25 Aug 2015 10:31:27 -0500	[thread overview]
Message-ID: <867fojidv4.fsf@stephe-leake.org> (raw)
In-Reply-To: <55DC5612.9050704@yandex.ru> (Dmitry Gutov's message of "Tue, 25 Aug 2015 14:48:34 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 08/25/2015 01:00 PM, Stephen Leake wrote:
>
>> To handle this, I propose changing both
>> xref-identifier-completion-table-function and xref-find-function to be
>> mode-local, instead of buffer-local.
>
> That seems unnecessarily limiting. First, mode-local facility is a
> part of CEDET, so it would need to be always loaded.

I realized after I posted that mode-local.el is not pre-loaded, so
elisp-mode.el can't require it. That said, mode-local.el is only one
file; nothing else in CEDET is required.

cl-generic.el is preloaded, so we could use a cl-defgeneric, and
dispatch on (mode (eql <major-mode>)).

> Second, how would a minor mode set an xref backend? It might not be
> tied to a particular major mode.

I don't see how a global minor mode can set an xref backend now.

To make such a minor mode work, xref--read-identifier could be a
cl-defgeneric that dispatches on (project <project-type). But if it also
dispatches on (mode (eql <major-mode>)), each backend would have to
define all combinations; that's a pain.

>> There are similar use cases; from a LaTeX document buffer, looking at the
>> description of an Ada function, find the Ada code that defines that
>> function. Or from a text mode notes file, look for a definition in any
>> one of several languages.
>
> All similar cases can be solved by a project-aware xref backend that
> knows about all languages used, and allows navigating to identifiers
> in all of them.

I've started writing such a thing, but it gets defeated by the fact that
xref--read-identifier uses the buffer-local value of
xref-identifier-completion-table-function, which is set by elisp-mode
(or c-mode, etc, or by default to etags). There's no way to change that.

We could require the user to manually enable an xref minor mode in each
buffer, but that's not friendly.

I guess a global xref backend could somehow reset that variable, in all
elisp buffers? Maybe a function on elisp-mode-hook.

The problem is that emacs-lisp-mode sets the buffer-local xref
variables, but I don't want it to.

So a better approach would be to define a way to disable emacs-lisp-mode
(and all other major-modes) setting the xref buffer-local variables, so
that the user choice of xref backend is respected. That would be much
simpler than having to add a function to all the major mode hooks (most
of which are unknown at load time).

We could define a new global variable xref-global-backend; if nil (the
default), major modes can set xref vars; if non-nil, it indicates which
particular global backend is in use. It could be a function that returns
a boolean indicating whether the global backend wants to control xref in
the current buffer. So a semi-global backend could provide C and Ada
xref, but not elisp xref, for example. It could be a list of such
functions; only if all return nil should the major mode set the xref
vars.

-- 
-- Stephe



  parent reply	other threads:[~2015-08-25 15:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 10:00 Allow xref to use other than current major-mode Stephen Leake
2015-08-25 11:48 ` Dmitry Gutov
2015-08-25 12:19   ` João Távora
2015-08-25 12:25   ` David Engster
2015-08-25 14:47     ` Stephen Leake
2015-08-25 15:07       ` David Engster
2015-08-25 15:23   ` Eli Zaretskii
2015-08-25 17:25     ` Dmitry Gutov
2015-08-25 21:17       ` Stephen Leake
2015-08-25 15:31   ` Stephen Leake [this message]
2015-08-25 15:41     ` Stephen Leake
2015-08-25 17:05     ` Dmitry Gutov
2015-08-25 21:13       ` Stephen Leake
2015-08-25 22:11         ` Dmitry Gutov
2015-08-25 22:15     ` Stefan Monnier
2015-08-25 22:29       ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867fojidv4.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).