bug#43609: 28.0.50; eldoc-documentation-function [vs new eldoc-display-functions]

[martin rudalics]

> I just pushed a cleaned-up improved version of the
> eldoc-display-functions branch.
>
> To git.sv.gnu.org:/srv/git/emacs.git
>  * [new branch]            scratch/eldoc-display-functions ->
> scratch/eldoc-display-functions

Thank you.  I had some autoload problems ('ede-add-project-autoload'
had a void function definition) so I had to bootstrap Emacs here which
took some time.

> After a cursory reading of it, I managed to adapt your eldoc-tooltip.el
> library to use it.  I didn't make many changes and didn't test it
> thoroughly, but I believe the adaptation works nicely.  I attach it as
> file eldoc-tooltip-joao.el.  It needs the eldoc-display-functions
> branch, obviously, which I will test for a few more than, then push to
> master (it's a straightforward planned change and seems pretty stable).

I tried that now and it doesn't work here for two reasons:

(1) It behaves like a solution that I worked out before you answered
my original report.  Both omit the function name when point is on that
name: For example, with point on 'setq' in (setq foo 3) I just get

([SYM VAL]...)

and no reference to the function itself as in the expected

setq: ([SYM VAL]...)

Or with point on some 'cons' I only get (CAR CDR).

(2) My pop-up-mini window child frame pops up whenever a tooltip is
immanent and shows the _expected_ full eldoc text in the echo area.

Now one aim of eldoc-tooltip is to show eldoc information in a separate
window near point and the other is to never show eldoc information in
the echo area so to avoid polluting the latter's contents and popping up
my minibuffer frame all the time.

But maybe also my set-up is wrong now - apparently I have to (1) enable
'global-eldoc-mode' in order to produce eldoc text and (2)
'eldoc-tooltip-mode' in order to show the text in a tooltip.  Is that
right?

martin