From: Lars Ingebrigtsen <larsi@gnus.org>
To: jidanni@jidanni.org
Cc: 139@debbugs.gnu.org
Subject: bug#139: describe-key vs. widget red tape
Date: Mon, 30 Sep 2019 07:56:58 +0200 [thread overview]
Message-ID: <877e5ql42d.fsf@gnus.org> (raw)
In-Reply-To: <87mynwgrxb.fsf@jidanni.org> (jidanni@jidanni.org's message of "Tue, 15 Apr 2008 03:25:20 +0800")
jidanni@jidanni.org writes:
> What will happen when I hit RET or click this mouse button here, I
> asked myself. Let's use trusty C-h k (describe-key).
>
> Nope. There's an extra layer of indirection involved apparently,
> and describe-key is not willing to cut through the red tape and give
> the ultimate answer along with its usual answer.
>
> <down-mouse-1> at that spot runs the command widget-button-click
> which is an interactive compiled Lisp function in `wid-edit.el'.
> It is bound to <down-mouse-1>, <down-mouse-2>.
> (widget-button-click EVENT)
[...]
> Nope. The only way to find out what will happen is to fasten one's
> seat belts and hit or click and find out.
>
> And even if there is a different incantation to find out, describe-key
> should also cough up the ultimate answer too.
I don't think there's any way that could work in general. Emacs knows
what down-mouse-1 calls, but it doesn't know about what that function in
turn does.
We could teach describe-key about certain common constructs, like
widgets and buttons, but that would be very ad hoc indeed, I think?
So I'm closing this bug report. If somebody else feels that
describe-key should start introspection of widgets/buttons, feel free to
reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-30 5:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 19:25 describe-key vs. widget red tape jidanni
2019-09-30 5:56 ` Lars Ingebrigtsen [this message]
2019-09-30 7:31 ` bug#139: " Eli Zaretskii
2019-09-30 7:40 ` Lars Ingebrigtsen
2019-09-30 8:25 ` Eli Zaretskii
2019-09-30 10:54 ` Mauro Aranda
2019-09-30 10:55 ` Mauro Aranda
2019-09-30 14:57 ` Lars Ingebrigtsen
2019-09-30 20:06 ` Mauro Aranda
2019-10-01 12:29 ` Lars Ingebrigtsen
2019-10-05 14:06 ` Mauro Aranda
2019-10-06 0:39 ` Basil L. Contovounesios
2019-10-07 1:55 ` Lars Ingebrigtsen
2019-10-08 13:04 ` Mauro Aranda
2019-10-11 14:38 ` Mauro Aranda
2019-10-11 15:23 ` Drew Adams
2019-10-11 18:57 ` Lars Ingebrigtsen
2020-08-07 11:16 ` Lars Ingebrigtsen
2020-08-07 11:38 ` Lars Ingebrigtsen
2020-10-31 1:32 ` bug#139: Still can't figure out what the command I used is called 積丹尼 Dan Jacobson
2020-10-31 2:55 ` Thien-Thi Nguyen
2020-10-31 10:33 ` 積丹尼 Dan Jacobson
2021-01-19 18:30 ` bug#139: describe-key vs. widget red tape Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e5ql42d.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=139@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.