From: "João Távora" <joaotavora@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Xref/Eglot feature requests and a question
Date: Fri, 25 Aug 2023 09:10:01 +0100 [thread overview]
Message-ID: <CALDnm50cXppiUPOnnODHwy11_OjofF3+-fiEkkZRxVT9zPtvzQ@mail.gmail.com> (raw)
In-Reply-To: <m2ttsnr4sv.fsf@Mini.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
Thanks, but please Gerd (and others), when creating bug reports for Eglot,
remember to Cc me directly (or X-Debbugs-CC me) in these emails as it
greatly helps me sort out my inbox and not lose track of this. I don't
always track emacs-devel and bug-gnu-emacs very closely.
João
On Fri, Aug 25, 2023, 07:54 Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> >> Date: Thu, 24 Aug 2023 15:33:23 +0200
> >>
> >> Feature request: Could eglot-mode do something like that?
> >> [...]
> >> In C mode, Xref works using Eglot, in ELisp mode it uses something else
> >> (I have no tags tables). 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.
> >
> > I suggest to submit 3 separate feature-request bug reports for these
> > two requests. The second one is for Eglot, the others for Xref, so
> > mixing them in a single issue is not recommended.
>
> 65520 normal Gerd Möllmann 30.0.50; [FR Xref] Project-wide
> operations
> 65519 normal Gerd Möllmann 30.0.50; [FR Eglot] keymaps for useful
> functions
> 65518 normal Gerd Möllmann 30.0.50; [FR Eglot] Completions over
> all workspace symbols
> 65517 normal Gerd Möllmann 30.0.50; Eglot: word list input
>
>
[-- Attachment #2: Type: text/html, Size: 2358 bytes --]
next prev parent reply other threads:[~2023-08-25 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 13:33 Xref/Eglot feature requests and a question Gerd Möllmann
2023-08-24 14:06 ` Visuwesh
2023-08-24 14:58 ` Eli Zaretskii
2023-08-25 6:53 ` Gerd Möllmann
2023-08-25 8:10 ` João Távora [this message]
2023-08-24 15:13 ` 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=CALDnm50cXppiUPOnnODHwy11_OjofF3+-fiEkkZRxVT9zPtvzQ@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).