From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#59149: Feature Request: Report progress of long requests in Eglot Date: Wed, 23 Nov 2022 19:56:27 +0000 Message-ID: References: <87educqkar.fsf@dfreeman.email> <86cz9jmg9r.fsf@stephe-leake.org> <87k03qvmla.fsf@dfreeman.email> <86fseckwvb.fsf@stephe-leake.org> <87tu2pohub.fsf@dfreeman.email> <86ilj5k0sn.fsf@stephe-leake.org> <87wn7l316m.fsf@dfreeman.email> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002559d105ee28ab3b" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5648"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59149@debbugs.gnu.org, stephen_leake@stephe-leake.org To: Danny Freeman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Nov 23 20:56:38 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oxvrJ-0001HH-ON for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 23 Nov 2022 20:56:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oxvqo-0004l0-0L; Wed, 23 Nov 2022 14:56:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oxvqm-0004j7-5o for bug-gnu-emacs@gnu.org; Wed, 23 Nov 2022 14:56:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oxvqk-0004de-Rm for bug-gnu-emacs@gnu.org; Wed, 23 Nov 2022 14:56:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oxvqk-0006GT-OR for bug-gnu-emacs@gnu.org; Wed, 23 Nov 2022 14:56:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 23 Nov 2022 19:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59149 X-GNU-PR-Package: emacs X-Debbugs-Original-Cc: 59149@debbugs.gnu.org, bug-gnu-emacs@gnu.org, Stephen Leake Original-Received: via spool by 59149-submit@debbugs.gnu.org id=B59149.166923332824034 (code B ref 59149); Wed, 23 Nov 2022 19:56:02 +0000 Original-Received: (at 59149) by debbugs.gnu.org; 23 Nov 2022 19:55:28 +0000 Original-Received: from localhost ([127.0.0.1]:56323 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oxvqC-0006FU-0R for submit@debbugs.gnu.org; Wed, 23 Nov 2022 14:55:28 -0500 Original-Received: from mail-oa1-f51.google.com ([209.85.160.51]:47057) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oxvqA-0006FA-Lc for 59149@debbugs.gnu.org; Wed, 23 Nov 2022 14:55:27 -0500 Original-Received: by mail-oa1-f51.google.com with SMTP id 586e51a60fabf-142faa7a207so9243142fac.13 for <59149@debbugs.gnu.org>; Wed, 23 Nov 2022 11:55:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=COF2U/aVkaDWos8/cLwM7bmtN5qluvKKTEGcvfaL2xE=; b=owmL6WlESvG4UTz4uw8IcphKMpg3KUXhzG3yWhQL4faZ//a+7HuEDJMd4jwULbibSM 0aRUGyNKBySCrezxbVrxSfqs82Fs8/s4NMys7TBmS38ekUWJXgBrhTXpHFRq5sgELB0D dI8Nr/YrQgV8x8zKFvuViYggBOvx9X0LYxaj5fSUT5b2NGOYqKFzjES5P4RAuaZOBSk8 SWVvCzb6oEDMITKTjZOrFQH9N5KjrOCVfYFIC1Zeg/xqtoakmHCysourkqHO8AVYypJP D8sfMuqmU6XlSBpYLPZ3/VSZiQCaHY5eeVKAw4oi617qvm3FicO1qQ3b3FtVln9cQGny RxRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=COF2U/aVkaDWos8/cLwM7bmtN5qluvKKTEGcvfaL2xE=; b=KhEtCtObMJtuJNFUWRIYR56JatUnXS4O0q1R2W9T90eIvITeensT+TNWA4wYA2nN+O UaQ1Tebw6R/KoafqLsHbBcB4+kKJhz5VVqEQxsxMAnL/5HZOPXqJ9r2IoPZiRo6GZWED P/b9rCS1dFYePuFIsrBDxj5+YuchC1plLHtko400ES8+BdJ61V3sgaaEJ1JPj3VqYI0b hkCEyok5HJSetuxq7hWaAJAhSCyjqwPbta6DQ5VhaScoouYbp1w+ipy99G+UrCXyWN9B EC/m/8//JYphQOJc8+8lO0FdD+zYxItZhyg+EZsuNmU8xmO0L1//VFqAkgd1Euo4g1+i dS/g== X-Gm-Message-State: ANoB5pmjnntBbHrVOxeJsBingWV8vaL3dRLNYNtlUkzOpSWWBXzLTc2o y65x+Cut6Vw4TCa340OG9zmH3lxvN7stpqbj7Bw= X-Google-Smtp-Source: AA0mqf5NnZLcbFcBa15RgGH56GZiBWT7j57tn8fY0ZlPLk7LB0aGKzMkoNeBWBi2XxSp4/LsSIf465iCb3ZYWS2JFhY= X-Received: by 2002:a05:6870:6688:b0:13b:5ffe:ff70 with SMTP id ge8-20020a056870668800b0013b5ffeff70mr18770723oab.171.1669233321006; Wed, 23 Nov 2022 11:55:21 -0800 (PST) In-Reply-To: <87wn7l316m.fsf@dfreeman.email> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:248779 Archived-At: --0000000000002559d105ee28ab3b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2022 at 7:45 PM Danny Freeman wrote: > > > Stephen Leake writes: > > I am copying him on this email, as I realize he wasn't on this branch of > the email chain. Jo=C3=A3o, 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=C3=A3o --0000000000002559d105ee28ab3b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 23, 2022 at 7:45 PM Danny Freeman <danny@df= reeman.email> wrote:
>
>
> Stephen Leake <stephen_leake@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=C3=A3o, please= see the previous emails in the thread for
> more context! Here is a = link for convenience:
> https://lists.gnu.org/archive/html/bu= g-gnu-emacs/2022-11/msg01619.html

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

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

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

Jo=C3=A3o
--0000000000002559d105ee28ab3b--