GNU bug report logs - #59149
Feature Request: Report progress of long requests in Eglot

Previous Next

Full log

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

From: João Távora <joaotavora <at> gmail.com>
To: Danny Freeman <danny <at> dfreeman.email>
Cc: 59149 <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org,
 Stephen Leake <stephen_leake <at> stephe-leake.org>
Subject: Re: bug#59149: Feature Request: Report progress of long requests in
 Eglot
Date: Wed, 23 Nov 2022 19:56:27 +0000

[Message part 1 (text/plain, inline)]

On Wed, Nov 23, 2022 at 7:45 PM Danny Freeman <danny <at> dfreeman.email> wrote:
>
>
> Stephen Leake <stephen_leake <at> stephe-leake.org> writes:
>
> I am copying him on this email, as I realize he wasn't on this branch of
> the email chain. João, please see the previous emails in the thread for
> more context! Here is a link for convenience:
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-11/msg01619.html

Yep this is all news to me, but no problem, I just read through the chain.

If, like Stephen says, $progress is part of the base protocol, then there's
no capability associated indeed, but I think we should just make up one
like `:$progress`, and use change eglot--server-capable-p to be able
to respond unequivocally 't' to those special built in capabilities, but
only after checking if they're not in the eglot-ignored-server-capabilities
list.

I think this is more consistent with the other kinds of feature checks we
have elsewhere.

João

[Message part 2 (text/html, inline)]

Previous Next

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