From: Stefan Kangas <stefankangas@gmail.com>
To: "Dave Abrahams" <dave@boostpro.com>,
"João Távora" <joaotavora@gmail.com>
Cc: 67870-done@debbugs.gnu.org, rms@gnu.org
Subject: bug#67870: 29.1; Eglot missing or un-findable advertised feature
Date: Sun, 24 Dec 2023 12:27:32 -0800 [thread overview]
Message-ID: <CADwFkmn2ky---LcofOPCpA3jrAzOyRaM4FQMqpr9iKaT6VUVug@mail.gmail.com> (raw)
In-Reply-To: <25F870BA-C37C-4C47-AD5B-D56273CDB0CD@boostpro.com>
Dave Abrahams <dave@boostpro.com> writes:
> I did suggest including certain words that would have helped me. Do
> you want a suggested rewrite of the text instead? What qualifies as a
> suggestion in your book?
I'm not João, but I see that he edited the text recently so that it now
reads, on current master:
• On-the-fly diagnostic annotations, via the Flymake package (*note
(flymake)Top::). Eglot's Flymake backend replaces other Flymake
backends while it is managing a buffer, and enhances diagnostics
with interactive server-suggested fixes (so-called “code actions”,
*note Eglot Commands::)
Does that seem okay to you or is there more we could do here?
Thanks.
prev parent reply other threads:[~2023-12-24 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 19:38 bug#67870: 29.1; Eglot missing or un-findable advertised feature Dave Abrahams
[not found] ` <handler.67870.B.17028419482015.ack@debbugs.gnu.org>
2023-12-17 20:23 ` bug#67870: Acknowledgement (29.1; Eglot missing or un-findable advertised feature) Dave Abrahams
2023-12-18 17:07 ` João Távora
2023-12-18 17:00 ` bug#67870: 29.1; Eglot missing or un-findable advertised feature João Távora
2023-12-18 19:10 ` Dave Abrahams
2023-12-18 19:59 ` João Távora
2023-12-19 8:15 ` Dave Abrahams
2023-12-19 8:51 ` João Távora
2023-12-22 3:14 ` Richard Stallman
2023-12-22 9:29 ` João Távora
2023-12-22 9:41 ` João Távora
2023-12-22 17:47 ` Dave Abrahams
2023-12-24 20:27 ` Stefan Kangas [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=CADwFkmn2ky---LcofOPCpA3jrAzOyRaM4FQMqpr9iKaT6VUVug@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=67870-done@debbugs.gnu.org \
--cc=dave@boostpro.com \
--cc=joaotavora@gmail.com \
--cc=rms@gnu.org \
/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.