bug#43609: 28.0.50; eldoc-documentation-function

[martin rudalics]

>> So 'eldoc-documentation-functions' just holds a list of functions I
>> could call in order to get the documentation of the object at point?
>> How does the notion of a "hook" enter here?
>
> It's a list that is usually manipulated with 'add-hook'. Like it often done 
with other variables named '*-functions'.

Its value is (elisp-eldoc-var-docstring elisp-eldoc-funcall t).  So what
am I supposed to do with that?  I would have to call these functions in
row with some function as callback argument that also handles the :thing
and :face stuff and produces and returns the doc string.

>>  > No, the hook functions are written already. They are basically a list
>>  > of functions that were previously the values of
>>  > eldoc-documentation-function. Except it's now a list. *And* they use
>>  > an asynchronous convention where the first argument they receive is a
>>  > callback.
>>
>> Is there a way to drop that callback?  I just want an immediate answer.
>
> With my proposal, there would have been. See the original discussion.

So there's no way to drop that callback and get an immediate answer.
Bad to know.

>> 'eldoc-documentation-strategy' is a variable so it's probably the
>> function that is the value of that variable and it should suffice to use
>> 'eldoc-documentation-default'.  But this failed here before.
>
> You should probably honor this variable, if the expectation is to generally 
follow ElDoc's behavior but display the documentation in a different place, e.g. 
using a popup.

Plain (funcall eldoc-documentation-strategy) gets me the already
familiar (void-function nil) error.

martin