From: Chong Yidong <cyd@stupidchicken.com>
To: jidanni@jidanni.org
Cc: yamaoka@jpl.org, 7727@debbugs.gnu.org, ding@gnus.org
Subject: Re: bug#7727: describe-key doesn't tell whole redirect sequence
Date: Sat, 22 Jan 2011 19:02:29 -0500 [thread overview]
Message-ID: <87r5c4bi7e.fsf@stupidchicken.com> (raw)
In-Reply-To: <87k4iznqjz.fsf_-_@jidanni.org> (jidanni@jidanni.org's message of "Fri, 24 Dec 2010 23:22:56 +0800")
jidanni@jidanni.org writes:
> KY> The real command that the "e" key is bound to in the article
> KY> buffer is `gnus-article-read-summary-keys'
>
> I see. So the real bug is in the describe-key function, not telling the
> user all the details! I'll Cc bug-gnu-emacs!
It's not a bug in describe-key, because that's apparently not the
command run by `C-h k' in Gnus article buffers:
C-h k runs the command gnus-article-describe-key, which is an
interactive compiled Lisp function in `gnus-art.el'.
It is bound to C-h k.
Indeed, doing `M-x describe-key' instead of `C-h k' returns
gnus-article-read-summary-keys, as expected. Dunno what the purpose of
gnus-article-describe-key is.
Bouncing back to the Gnus developers.
next prev parent reply other threads:[~2011-01-23 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 2:40 (put 'gnus-summary-edit-article 'disabled t) doesn't work in *Article* buffer jidanni
2010-12-24 12:00 ` Katsumi Yamaoka
2010-12-24 15:22 ` describe-key doesn't tell whole redirect sequence jidanni
2011-01-02 5:58 ` Lars Magne Ingebrigtsen
2011-01-23 0:02 ` Chong Yidong [this message]
2011-01-23 1:19 ` bug#7727: " Lars Ingebrigtsen
2011-01-24 1:04 ` Lars Ingebrigtsen
2011-01-24 1:24 ` Lars Ingebrigtsen
2011-01-24 16:31 ` bug#7727: " Stefan Monnier
2011-01-24 22:01 ` Lars Ingebrigtsen
2011-01-25 3:09 ` Stefan Monnier
2011-01-25 9:31 ` 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=87r5c4bi7e.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=7727@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.org \
--cc=yamaoka@jpl.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.
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 NNTP newsgroup(s).