all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 65520@debbugs.gnu.org
Subject: bug#65520: 30.0.50; [FR Xref] Project-wide operations
Date: Fri, 25 Aug 2023 10:21:34 +0300	[thread overview]
Message-ID: <83jztjoadd.fsf@gnu.org> (raw)
In-Reply-To: <m2y1hzr50i.fsf@Mini.fritz.box> (message from Gerd Möllmann on Fri, 25 Aug 2023 08:49:01 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Fri, 25 Aug 2023 08:49:01 +0200
> 
> In C mode, Xref works using Eglot, in ELisp mode it uses something else
> (I have no tags tables; don't know how that works).

It works by using the ELisp's own backend.

> Both work really
> well, but I apparently have to be in an ELisp buffer to use one and in a
> C buffer to use the other.
> 
> Feature request: Is it possible to use more than one backend at the same
> time?  So that I could C-M-. to find an ELisp function while being in a
> C file?  I couldn't find something like that mentioned in the docs, so I
> guess it's not yet possible.

Probably not what you had in mind, but "M-x xref-etags-mode" will
cause ELisp to use etags as well, and then you can have what you want
(at least in Emacs) with a single backend.





      parent reply	other threads:[~2023-08-25  7:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  6:49 bug#65520: 30.0.50; [FR Xref] Project-wide operations Gerd Möllmann
2023-08-25  7:03 ` Gerd Möllmann
2023-08-25  7:48   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-25 16:26     ` Dmitry Gutov
2023-08-25  8:26   ` Gerd Möllmann
2023-08-25 16:17   ` Dmitry Gutov
2023-08-26  5:22     ` Gerd Möllmann
2023-08-25 16:20   ` Dmitry Gutov
2023-08-26  5:31     ` Gerd Möllmann
2023-08-27  0:32       ` Dmitry Gutov
2023-08-27  6:32         ` Gerd Möllmann
2023-08-25  7:21 ` Eli Zaretskii [this message]

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

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

  git send-email \
    --in-reply-to=83jztjoadd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65520@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.