unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 65518@debbugs.gnu.org
Subject: bug#65518: 30.0.50; [FR Eglot] Completions over all workspace symbols
Date: Sat, 26 Aug 2023 09:57:12 +0100	[thread overview]
Message-ID: <CALDnm52WLZv5MDNvjJOHFYgWSPk1Auj8+eE7SsPzsy+3M-rrDw@mail.gmail.com> (raw)
In-Reply-To: <m2zg2ee6et.fsf@Mini.fritz.box>

On Sat, Aug 26, 2023 at 6:09 AM Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
> > Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> >

> We are miscommunicating.  This is not a bug report, it's a feature
> request. Referring me to a description of how to produce reproducible
> bug reports I therefore find odd.


Please don't find it odd.  And we are miscommunicating indeed.

Let me be clear: as far as I can detect, and as far as I can understand
it, the situation you describe shouldn't exist.  The pattern `LiPa` should
eventually allow the completion `Lisp_Package` to be offered in theory.

I reach all my completions with similar abbreviated patterns for
example.

But perhaps you aren't using Eglot how I think you are using it.
Perhaps you are using some older clangd version (known to miss completions)
or perhaps you are using some popular "Corfu" package (also known
to miss completions).  Or perhaps there is a indeed bug in Eglot.

Therefore, to give you an and others readers a useful answer,
I must have more information.  And providing the information
in that recipe is the standard way I ask of all Eglot users.

So to continue the analysis of this, I beg you to provide it.
If you don't want to go through that list, I've already collected
some information, so it boils down to telling me:

1. Emacs version and Eglot version
2. Clangd version
3. How to produce your compile_commands.json file
4. What branch of the Emacs C source this is
5. A short description of exactly what you do after starting
Emacs -Q, what you see, and what you would like to see instead.

> As I mentioned, lsp-mode offers the functionality, that I'd like to see in
> Eglot.  I don't know how it does it, and I don't care, really.

If you want a comparative analysis to lsp-mode, to increase
the chances that this is addressed, I'd also need to know exactly
how you set it up.  As far as I understand, lsp-mode doesn't
do miracles, it uses the same LSP interfaces available to Eglot
(in this case, more than likely `symbol/workspace`, which I've
already described).

João





  reply	other threads:[~2023-08-26  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  6:44 bug#65518: 30.0.50; [FR Eglot] Completions over all workspace symbols Gerd Möllmann
2023-08-25  9:22 ` João Távora
2023-08-26  5:09   ` Gerd Möllmann
2023-08-26  8:57     ` João Távora [this message]
2023-08-27  0:14       ` João Távora
2023-08-27  5:56         ` Gerd Möllmann
2023-08-27  6:06           ` João Távora
2023-08-27  6:38             ` Gerd Möllmann
2023-08-28  0:19   ` Dmitry Gutov
2023-08-28 11:10     ` Gerd Möllmann

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=CALDnm52WLZv5MDNvjJOHFYgWSPk1Auj8+eE7SsPzsy+3M-rrDw@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=65518@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 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).