From: "João Távora" <joaotavora@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: casouri@gmail.com, 43609@debbugs.gnu.org
Subject: bug#43609: 28.0.50; eldoc-documentation-function [vs new eldoc-display-functions]
Date: Mon, 05 Oct 2020 10:29:50 +0100 [thread overview]
Message-ID: <87362tggvl.fsf@gmail.com> (raw)
In-Reply-To: <d094af1b-0cd9-3527-407a-3f8c9c5122c9@gmx.at> (martin rudalics's message of "Mon, 5 Oct 2020 10:35:52 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> 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.
I had the same problem: it appeared in Emacs master recently.
>> 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
Right, as I said, this is to show you how eldoc-display-function works,
not to fix your library definitely. Anyway, in the
eldoc-tooltip-joao.el file I gave you, I passed the function #'car to
mapconcat, right? This was just a quick and lazy solution: to get that
augmented information you have to pass it a function that uses more
properties of the list that represent a piece of documentation. But I
think the previous 'martin' function I gave you should have exactly that
string producing function inside it, right?
> (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.
Makes perfect sense I guess. You should be able to
(remove-hook 'eldoc-display-functions 'eldoc-display-in-echo-area)
If you're not a fan of the echo area display.
> 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?
Yes, it is. But do you really need a minor mode? I think activating
your extension could be a matter of:
(remove-hook 'eldoc-display-functions 'eldoc-display-in-martins-tooltip)
instead of a global minor mode. Then you would let ElDoc mode _drive_
your extension.
next prev parent reply other threads:[~2020-10-05 9:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:46 bug#43609: 28.0.50; eldoc-documentation-function martin rudalics
2020-09-26 18:34 ` Dmitry Gutov
2020-09-27 8:30 ` martin rudalics
2020-09-29 11:20 ` Dmitry Gutov
2020-09-29 15:09 ` martin rudalics
2020-09-29 15:23 ` Dmitry Gutov
2020-09-30 8:14 ` martin rudalics
2020-09-30 8:50 ` Dmitry Gutov
2020-09-30 14:37 ` João Távora
2020-09-30 17:33 ` martin rudalics
2020-09-30 18:22 ` João Távora
2020-10-01 8:40 ` martin rudalics
2020-10-01 9:23 ` João Távora
2020-10-03 19:15 ` bug#43609: 28.0.50; eldoc-documentation-function [vs new eldoc-display-functions] João Távora
2020-10-05 8:35 ` martin rudalics
2020-10-05 9:29 ` João Távora [this message]
2020-10-06 8:23 ` martin rudalics
2020-10-06 9:29 ` João Távora
2020-10-07 8:36 ` martin rudalics
2020-10-07 8:40 ` João Távora
2020-10-07 9:36 ` João Távora
2020-10-08 8:22 ` martin rudalics
2020-10-08 8:27 ` João Távora
2020-10-09 8:03 ` martin rudalics
2020-10-24 15:18 ` João Távora
2020-10-26 14:12 ` João Távora
2020-10-27 9:59 ` martin rudalics
2020-10-27 9:58 ` martin rudalics
2020-10-27 15:11 ` João Távora
2020-10-27 18:05 ` martin rudalics
2020-10-27 19:56 ` João Távora
2020-10-28 8:39 ` martin rudalics
2020-10-28 9:38 ` João Távora
2020-10-31 8:01 ` martin rudalics
2020-10-28 9:17 ` Lars Ingebrigtsen
2020-10-28 9:54 ` João Távora
2020-10-30 22:51 ` João Távora
2020-10-31 8:02 ` martin rudalics
2020-10-23 2:37 ` Yuan Fu
2020-10-24 17:09 ` João Távora
2020-10-31 13:07 ` Basil L. Contovounesios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87362tggvl.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=43609@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).