From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: christopher@librehacker.com, 74673@debbugs.gnu.org,
kevin.legouguec@gmail.com
Subject: bug#74673: 30.0.92; face warning on legal elisp syntax
Date: Thu, 05 Dec 2024 11:53:37 +0200 [thread overview]
Message-ID: <867c8exxpa.fsf@gnu.org> (raw)
In-Reply-To: <87cyi6cwbs.fsf@gmail.com> (message from Robert Pluim on Thu, 05 Dec 2024 10:28:55 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Kévin Le Gouguec <kevin.legouguec@gmail.com>,
> christopher@librehacker.com, 74673@debbugs.gnu.org
> Date: Thu, 05 Dec 2024 10:28:55 +0100
>
> >>>>> On Wed, 04 Dec 2024 19:32:54 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> >> Cc: Christopher Howard <christopher@librehacker.com>, 74673@debbugs.gnu.org
> >> Date: Wed, 04 Dec 2024 18:12:06 +0100
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> > Some nice features of the UI need the mouse, yes, and there's no
> >> > (easy) way around that. That said, you can go to the "" part and type
> >> > "M-x describe-text-properties", which will pop a buffer that tells you
> >> > there's a help-echo property at that spot, and show a button which you
> >> > could press to have the text shown in the echo-area.
> >> >
> >> > If you really need to be able to show tool tips without the mouse, you
> >> > can write a simple function to show its text in the echo-area.
> >> > However, most tooltips are shown on UI parts where you cannot go, so
> >> > such a command will be of somewhat limited use.
> >>
> >> Apologies if I missed something: this specific diagnostic is also
> >> visible with 'C-h .', right?
>
> Eli> Yes.
>
> You could do something like this to economise on typing:
>
> (defun display-help-string ()
> (when-let* ((help (help-at-pt-kbd-string)))
> (message "%s" (substitute-command-keys help))))
> (add-hook 'post-command-hook #'display-help-string nil t)
>
> (hmm, would it make sense to add something like that to eldoc?)
Given that we already have help-at-pt-display-when-idle, why is
anything else needed?
next prev parent reply other threads:[~2024-12-05 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 18:49 bug#74673: 30.0.92; face warning on legal elisp syntax Christopher Howard
2024-12-03 19:02 ` Eli Zaretskii
2024-12-03 19:19 ` Christopher Howard
2024-12-03 19:38 ` Eli Zaretskii
2024-12-03 20:48 ` Christopher Howard
2024-12-04 12:23 ` Eli Zaretskii
2024-12-04 17:12 ` Kévin Le Gouguec
2024-12-04 17:32 ` Eli Zaretskii
2024-12-05 9:28 ` Robert Pluim
2024-12-05 9:53 ` Eli Zaretskii [this message]
2024-12-05 10:06 ` Robert Pluim
2024-12-04 17:51 ` Jim Porter
2024-12-04 18:55 ` Eli Zaretskii
2024-12-06 4:46 ` Richard Stallman
2024-12-06 8:26 ` Eli Zaretskii
2024-12-04 15:42 ` Christopher Howard
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=867c8exxpa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74673@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=kevin.legouguec@gmail.com \
--cc=rpluim@gmail.com \
/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).