[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59149: Feature Request: Report progress of long requests in Eglot
From: |
Stephen Leake |
Subject: |
bug#59149: Feature Request: Report progress of long requests in Eglot |
Date: |
Wed, 23 Nov 2022 10:01:28 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Danny Freeman <danny@dfreeman.email> writes:
> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> I just ran into the progress reporter in eglot--apply-text-edits; I'd
>> like to turn that off, but leave other progress-reporters on.
>>
>> So we need something more fine-grained:
>>
>> (setq eglot-progress-reporter-disable '(apply-text-edits))
>
> I believe that is a different progress reporter, unrelated to the one I
> would like to introduce. It is not a progress report that come from the
> lsp server, so I don't think it would be good to conflate them.
True, but how is the user to know where it comes from? We could provide
something like:
eglot-server-progress-reporter-disable
eglot-client-progress-reporter-disable
How does the user know which to set? They'll just set both, so there
might as well be only one.
> If the user wants to ignore specific progress indicators from the lsp
> servers then they could implement an empty version of
> eglot-handle-notification that matches their progress token.
I guess that's a reasonable starting point, but it doesn't work for
apply-text-edits.
> The result of this patch is a series of messages that display in the
> minibuffer:
>
> ```
> [eglot:website] clojure-lsp:
> [eglot:website] clojure-lsp: 5% Finding kondo config
...
And the user can still use the minibuffer for find-file etc; the
messages are displayed to the right. Which can be confusing at first,
but works nicely.
--
-- Stephe
- bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/09
- bug#59149: Feature Request: Report progress of long requests in Eglot, João Távora, 2022/11/10
- bug#59149: Feature Request: Report progress of long requests in Eglot, Stephen Leake, 2022/11/19
- bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/19
- bug#59149: Feature Request: Report progress of long requests in Eglot, Stephen Leake, 2022/11/21
- bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/23
- bug#59149: Feature Request: Report progress of long requests in Eglot,
Stephen Leake <=
- bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/23
- bug#59149: Feature Request: Report progress of long requests in Eglot, João Távora, 2022/11/23
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Stephen Leake, 2022/11/24
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, João Távora, 2022/11/24
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Stephen Leake, 2022/11/24
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, João Távora, 2022/11/25
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/25
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Eli Zaretskii, 2022/11/25
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/25
- bug#59149: [SPAM UNSURE] Re: bug#59149: Feature Request: Report progress of long requests in Eglot, Danny Freeman, 2022/11/25