GNU bug report logs - #62538
29.0.60; Setting eglot-report-progress dir-locally doesn't work

Previous Next

Package: emacs;

Reported by: Augusto Stoffel <arstoffel <at> gmail.com>

Date: Thu, 30 Mar 2023 07:57:02 UTC

Severity: normal

Found in version 29.0.60

To reply to this bug, email your comments to 62538 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to joaotavora <at> gmail.com, bug-gnu-emacs <at> gnu.org:
bug#62538; Package emacs. (Thu, 30 Mar 2023 07:57:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Augusto Stoffel <arstoffel <at> gmail.com>:
New bug report received and forwarded. Copy sent to joaotavora <at> gmail.com, bug-gnu-emacs <at> gnu.org. (Thu, 30 Mar 2023 07:57:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Augusto Stoffel <arstoffel <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.0.60; Setting eglot-report-progress dir-locally doesn't work
Date: Thu, 30 Mar 2023 09:56:43 +0200
I set eglot-report-progress to nil in the "nil" section of my project's
.dir-locals.el, but I still see progress reports in the mode line.

If I add a debug message to the corresponding eglot-handle-notification
method, I see that the "(when eglot-report-progress" is evaluated in a
temp buffer and so doesn't pick up the dir-local value.

(By the way, Eglot was feeling very sluggish until I decided to disable
these notifications.  It reminded me of a similar situation with garbage
collection, where disabling a message changed user's perception of
latency in the process.  Or is this an urban legend?)




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#62538; Package emacs. (Thu, 30 Mar 2023 08:18:02 GMT) Full text and rfc822 format available.

Message #8 received at 62538 <at> debbugs.gnu.org (full text, mbox):

From: João Távora <joaotavora <at> gmail.com>
To: Augusto Stoffel <arstoffel <at> gmail.com>
Cc: 62538 <at> debbugs.gnu.org
Subject: Re: bug#62538: 29.0.60; Setting eglot-report-progress dir-locally
 doesn't work
Date: Thu, 30 Mar 2023 09:19:25 +0100
Augusto Stoffel <arstoffel <at> gmail.com> writes:

> I set eglot-report-progress to nil in the "nil" section of my project's
> .dir-locals.el, but I still see progress reports in the mode line.
>
> If I add a debug message to the corresponding eglot-handle-notification
> method, I see that the "(when eglot-report-progress" is evaluated in a
> temp buffer and so doesn't pick up the dir-local value.

Ah.  It wasn't meant to be used buffer-locally.  But if it's an easy
fix, there so reason it shouldn't be.

> (By the way, Eglot was feeling very sluggish until I decided to disable
> these notifications.  It reminded me of a similar situation with garbage
> collection, where disabling a message changed user's perception of
> latency in the process.  Or is this an urban legend?)

OK I will see what I can do.

João




This bug report was last modified 1 year and 26 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.