From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 72765@debbugs.gnu.org
Subject: bug#72765: Eglot + Clangd + Company + non-empty suffix = duplicate text
Date: Tue, 10 Sep 2024 04:40:08 +0300 [thread overview]
Message-ID: <922f8522-2d41-40bc-a83b-ed9d378e92fd@gutov.dev> (raw)
In-Reply-To: <CALDnm50eGAGXyRPhysALmDKHbZ3sJz8+1UmMkAQDBG9y5vs3Tw@mail.gmail.com>
Hi Joao,
On 08/09/2024 18:51, João Távora wrote:
> So, for the record, before this patch with the latest emacs-30, I get the
> results in failure1.txt
I've taken some more looks at the test output.
[eglot-tests] contents of `*EGLOT (cmpl-project/(rust-mode
rust-ts-mode)) output*':
> [eglot-tests] contents of `nil':
> [eglot-tests] Killing (main.rs), wiping /tmp/eglot--fixture-XCmCqo
> Test eglot-test-rust-completion-exit-function backtrace:
> set-buffer(#<killed buffer>) eglot--call-with-fixture((("cmpl-project" ("main.rs" . "fn test() ->Test eglot-test-rust-completion-exit-function condition:
> (error "Selecting deleted buffer")
This error comes from eglot--call-with-fixture, where one of the last
(with-current-buffer buffer (buffer-string))
calls results in "Selecting deleted buffer" error. I'm not sure where
that comes from (for the duration of the log the contents of stdout
buffer are printed twice, and stderr and events just once -- somehow
there are two elements inside the 'new-servers' var).
That hid the original problem, which was just that in the bare session
yasnippet is not available. Not sure what to do about it -
monkeypatching a replacements does not seem wise - but if we adjust the
"expected" at the end not to have parens, then the test finally passes.
It will fail interactively, though, when yasnippet is installed.
I've pushed that fix as
https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-30&id=818c0cc9a51a1d678749404cdacdf640d6f32d6e
now.
It makes that test more similar to
'eglot-test-try-completion-inside-symbol', but testing rust-analyzer
separately still seems like a plus.
prev parent reply other threads:[~2024-09-10 1:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 23:07 bug#72765: Eglot + Clangd + Company + non-empty suffix = duplicate text Dmitry Gutov
2024-08-29 11:34 ` Eli Zaretskii
2024-08-30 21:23 ` Dmitry Gutov
2024-08-31 6:47 ` Eli Zaretskii
2024-08-31 12:03 ` João Távora
2024-09-01 1:43 ` Dmitry Gutov
2024-09-01 9:43 ` João Távora
2024-09-01 14:28 ` Dmitry Gutov
2024-09-03 13:20 ` Dmitry Gutov
2024-09-03 13:43 ` João Távora
2024-09-08 2:41 ` Dmitry Gutov
2024-09-08 15:51 ` João Távora
2024-09-09 0:20 ` Dmitry Gutov
2024-09-09 11:46 ` Eli Zaretskii
2024-09-10 0:58 ` Dmitry Gutov
2024-09-10 11:47 ` Eli Zaretskii
2024-09-10 13:20 ` Dmitry Gutov
2024-09-10 1:40 ` Dmitry Gutov [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
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=922f8522-2d41-40bc-a83b-ed9d378e92fd@gutov.dev \
--to=dmitry@gutov.dev \
--cc=72765@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@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).