From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: jp@neverwas.me, philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: New Eglot release
Date: Fri, 10 Mar 2023 14:23:33 +0200 [thread overview]
Message-ID: <83lek4ztfe.fsf@gnu.org> (raw)
In-Reply-To: <87jzzoj0oy.fsf@gmail.com> (message from João Távora on Fri, 10 Mar 2023 11:38:37 +0000)
> From: João Távora <joaotavora@gmail.com>
> Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org, eliz@gnu.org
> Date: Fri, 10 Mar 2023 11:38:37 +0000
>
> Eli, is this patch good to push? It adds a new etc/EGLOT-NEWS and makes
> a tiny mention to it in etc/NEWS.
EGLOT-NEWS mentions many bugfixes, something that we don't do in
NEWS. The style is also very different:
> +(github#29)
> +
> +** Handle experimental/unknown server methods gracefully.
This doesn't say enough about the change, so why mention it? And why
the GitHub reference there?
> +** Hierarchical symbols are supported in Imenu.
> +Thanks to Ingo Lohmar for the original implementation (github#303).
We don't mention individual contributors in NEWS. They are mentioned
in AUTHORS instead (and if you want, also in doc/emacs/ack.texi).
> +(github#196)
> +
> +** Completion sorting fixed.
This (and other similar entries) are not very useful, IMNSHO.
Moreover, I don't think I see why mentioning past versions of Eglot
that were never parts of Emacs would be useful to someone. It might
be okay to have that on ELPA, but I don't see why we'd want this in
Emacs core.
> +mode: outline
> +mode: bug-reference-mode
Why not emacs-news-mode?
> +Please send Eglot bug reports to 'bug-gnu-emacs@gnu.org', and Cc (or
> +X-Debbugs-CC) the maintainer 'joaotavora@gmail.com' as well. Please
> +read the chapter titled "Troubleshooting" in the Eglot manual,
> +available https://joaotavora.github.io/eglot/#Troubleshooting-Eglot
The Eglot manual is now part of Emacs, not on GitHub.
next prev parent reply other threads:[~2023-03-10 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 20:02 New Eglot release João Távora
2023-03-05 5:50 ` Eli Zaretskii
2023-03-05 9:09 ` Michael Albinus
2023-03-05 15:30 ` João Távora
2023-03-05 15:37 ` Dmitry Gutov
2023-03-05 15:47 ` Eli Zaretskii
2023-03-05 15:56 ` Philip Kaludercic
2023-03-05 22:15 ` João Távora
2023-03-06 17:33 ` Philip Kaludercic
2023-03-06 17:33 ` Philip Kaludercic
2023-03-07 14:54 ` F. Jason Park
2023-03-10 11:38 ` João Távora
2023-03-10 12:23 ` Eli Zaretskii [this message]
2023-03-10 12:50 ` João Távora
2023-03-10 13:06 ` Eli Zaretskii
2023-03-10 13:42 ` João Távora
2023-03-11 15:11 ` Michael Albinus
2023-03-11 20:16 ` João Távora
2023-03-12 6:23 ` Eli Zaretskii
2023-03-12 19:12 ` João Távora
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=83lek4ztfe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=jp@neverwas.me \
--cc=philipk@posteo.net \
/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).