From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jp@neverwas.me, philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: New Eglot release
Date: Fri, 10 Mar 2023 12:50:27 +0000 [thread overview]
Message-ID: <CALDnm51FrL16XsqdagsHVBUQa4rboKa_0FWuZ=650i08PeSFBQ@mail.gmail.com> (raw)
In-Reply-To: <83lek4ztfe.fsf@gnu.org>
On Fri, Mar 10, 2023 at 12:23 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > 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:
Yes, it's quite different and this is in big part why I opted for
a separate file, so hopefully these idiosyncrasies could be
at least tolerated.
> > +(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?
For readers to get access to the original context. This was all
pre-merge, and at the time I decided as maintainer that that would
be the kind of NEWS file that I would like to read.
> > +** 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).
Yeah, again pre-merge. At the time I didn't have an AUTHORS file and
I wanted to thank certain contributors specially for certain
contributions. Shall I remove these mentions? (Sorry Ingo :-) )
> > +(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,
Eglot is a :core GNU ELPA package, meaning its source files and its
documentation lives in the Emacs.git repo.
> but I don't see why we'd want this in Emacs core.
I think it's quite nice to have a historical record of Eglot's
evolution, to see how far it has come, how certain decisions were
taken and adjusted over the years.
> > +mode: outline
> > +mode: bug-reference-mode
>
> Why not emacs-news-mode?
Because, for some reason I didn't investigate, it erases my
bug-reference-bug-regexp and the links stop working.
> > +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.
When Emacs 29 is releasd, probably the Eglot manual will be in GNU
sites _for that release, but not for all the other intermediate releases
of the :core ELPA package.
AFAIK, the only place where an up-to-date version is published
for users to read is that link (I'm happy to be shown otherwise, so
I don't have to do this periodic chore anymore).
João
next prev parent reply other threads:[~2023-03-10 12:50 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
2023-03-10 12:50 ` João Távora [this message]
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='CALDnm51FrL16XsqdagsHVBUQa4rboKa_0FWuZ=650i08PeSFBQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).