[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Calling eldoc-message directly
From: |
Clément Pit-Claudel |
Subject: |
Re: Calling eldoc-message directly |
Date: |
Wed, 9 May 2018 22:43:04 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 2018-05-09 22:01, Stefan Monnier wrote:
>> In that package, I use a server process to get information about the current
>> buffer. I can use it to asynchronously retrieve documentation about
>> identifiers, among other things. This pattern seems pretty common (I think
>> that's how tide, elpy, cider, and multiple other modes work).
>
> Indeed async use is currently not supported.
>
> Not sure how to best add support for sync-processing.
> Ideally, we'd pass a "continuation" to the eldoc-documentation-function,
> but that would break existing functions which wouldn't expect that extra arg.
>
> We could pass that extra arg via a dynamically-scoped variable like
> `eldoc-continuation-function`.
>
> An alternative would be to allow eldoc-documentation-function to return
> a function, which is then called with the continuation.
That would be nice. This model works pretty well in company-mode.