all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 65520@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#65520: 30.0.50; [FR Xref] Project-wide operations
Date: Sat, 26 Aug 2023 07:22:11 +0200	[thread overview]
Message-ID: <m2r0nqe5to.fsf@Mini.fritz.box> (raw)
In-Reply-To: <929f86c4-edb6-46f5-f24c-3b46054a0ad4@gutov.dev> (Dmitry Gutov's message of "Fri, 25 Aug 2023 19:17:14 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

> On 25/08/2023 10:03, Gerd Möllmann wrote:
>> My mental model is like so: I'm in a Git repo (Emacs), which is, I think
>> also a project in the project.el sense.  This project contains differnt
>> sets of files for which information is available using different
>> backends (Eglot, Etags, others depending on the kind of project).  What
>> U'd like to have is something on the level of such a project, if you
>> know what mean.  That is, M-. would take all available info for such a
>> project into account.
>
> One possible alternative is to treat this situation not like a new
> feature, and write a specialized new Xref backend which would collect
> both the info from Lisp and from TAGS when you are anywhere inside the
> Emacs sources. It shouldn't take too many lines either.
>
> The current existing alternative for that, like Eli pointed out, is
> xref-etags-mode: it disables Elisp's own backend and just uses TAGS
> everywhere ('make tags' in Emacs generates tags for Lisp functions as
> well). With the natural downside that you would need to regen tags
> manually for both types of files now. And that you're using Eglot
> instead ;-(.

Yeah ;-).  That's not what I was looking for. 





  reply	other threads:[~2023-08-26  5:22 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 [this message]
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

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=m2r0nqe5to.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=65520@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=visuweshm@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.