From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 139@debbugs.gnu.org
Subject: bug#139: Still can't figure out what the command I used is called
Date: Sat, 31 Oct 2020 09:32:23 +0800 [thread overview]
Message-ID: <87r1pfrxi0.8.fsf@jidanni.org> (raw)
In-Reply-To: <87mynwgrxb.fsf@jidanni.org>
10 years later. gnus-version "Gnus v5.13" emacs-version "27.1"
If some click / press can do some action,
then surely "C-h k runs the command describe-key"
can, somewhere in its output, tell me what that does.
I mean say poking around, clicking things left and right, I found a neat
command. But what is it? It is neat, but has no name I can dig up.
We do C-h k RET, but of course "the secretary won't let us see what the
command finally points to":
RET runs the command gnus-article-press-button (found in
gnus-mime-button-map), which is an interactive compiled Lisp function
in ‘gnus-art.el’.
It is bound to RET, <menu-bar> <MIME Part> <Toggle Display>.
(gnus-article-press-button)
Check text at point for a callback function.
If the text at point has a ‘gnus-callback’ property,
call it with the value of the ‘gnus-data’ text property.
Same with
<down-mouse-1> at that spot runs the command mouse-drag-region (found
in global-map), which is an interactive compiled Lisp function in
‘mouse.el’...
What they finally (dynamically) point to is still 'top secret' in
emacs-version "27.1".
next prev parent reply other threads:[~2020-10-31 1:32 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 ` bug#139: " Lars Ingebrigtsen
2019-09-30 7:31 ` 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 ` 積丹尼 Dan Jacobson [this message]
2020-10-31 2:55 ` bug#139: Still can't figure out what the command I used is called 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
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=87r1pfrxi0.8.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=139@debbugs.gnu.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 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).