From: Stefan Kangas <stefankangas@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Jacky Li <drsl@drshapeless.com>, 66435@debbugs.gnu.org
Subject: bug#66435: 30.0.50; Eglot no longer log status in minibuffer
Date: Sun, 21 Jan 2024 04:15:31 -0600 [thread overview]
Message-ID: <CADwFkm=s3MRYZ06XpV-xCdW+f+u33G=B-hRSdaVWqz5QOd960A@mail.gmail.com> (raw)
In-Reply-To: <CALDnm50ibq=JeWo16PQub4jNHMhs4e-yRcgCRFLaAL6zewOiBA@mail.gmail.com>
tags 66435 + notabug
thanks
João Távora <joaotavora@gmail.com> writes:
> On Wed, Jan 10, 2024, 18:09 Stefan Kangas <stefankangas@gmail.com> wrote:
>
>> Jacky Li <drsl@drshapeless.com> writes:
>>
>> > When I compile and use the master branch of Emacs, Eglot no longer shows
>> > its status in the minibuffer.
>> >
>> > It used to show some information in 29.1 when opening a file in a new
>> > project, which bootstrap the lsp server. After I downgraded to 29.1, the
>> > log reappears.
>> >
>> > I am not sure what change in version 30 is causing the problem. I am not
>> > sure whether this is intended or not.
>>
>> João, any comments?
>>
>
> If by "status", Jackie is talking about progress indication, then this NEWS
> entry pertaining to 1.14 might be relevant:
>
> ** Progress indicators inhabit the mode-line by default
>
> To switch to the echo area, customize 'eglot-report-progress' to
> 'messages'. To switch off progress reporting completely, set to nil.
>
> This was requested by many users who saw their echo area spammed in some
> servers. In e new version, the messages can be read by hovering over the
> percentage indication in the mode-line.
It sounds like this is the intended behavior, so I'm closing this bug
report.
next prev parent reply other threads:[~2024-01-21 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 11:34 bug#66435: 30.0.50; Eglot no longer log status in minibuffer Jacky Li via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 18:09 ` Stefan Kangas
2024-01-10 19:44 ` João Távora
2024-01-21 10:15 ` Stefan Kangas [this message]
2024-02-02 7:31 ` Stefan Kangas
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='CADwFkm=s3MRYZ06XpV-xCdW+f+u33G=B-hRSdaVWqz5QOd960A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=66435@debbugs.gnu.org \
--cc=drsl@drshapeless.com \
--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).