unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: New Eglot release
Date: Sun, 05 Mar 2023 17:47:23 +0200	[thread overview]
Message-ID: <83ilff8ak4.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm53fWyHhVmR2DAqAKXdBhMpUFvtSrpqxpU-3yaJ99BrE3A@mail.gmail.com> (message from João Távora on Sun, 5 Mar 2023 15:30:19 +0000)

> From: João Távora <joaotavora@gmail.com>
> Date: Sun, 5 Mar 2023 15:30:19 +0000
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> On Sun, Mar 5, 2023, 05:50 Eli Zaretskii <eliz@gnu.org> wrote:
> 
>  Sorry, I don't follow what you say here, and thus don't understand the
>  difficulty.  Perhaps if you show the text you'd like to have there,
>  the misunderstanding will be resolved.
> 
> A mention to Eglot's new support for LSP inlay hints, for example.

That should be in NEWS, I think.

In general, if the new Eglot release doesn't have dozens of new
features, I'd suggest to describe them all in NEWS.



  parent reply	other threads:[~2023-03-05 15:47 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 [this message]
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
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=83ilff8ak4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).