From: jidanni@jidanni.org
To: yamaoka@jpl.org
Cc: ding@gnus.org,bug-gnu-emacs@gnu.org
Subject: describe-key doesn't tell whole redirect sequence
Date: Fri, 24 Dec 2010 23:22:56 +0800 [thread overview]
Message-ID: <87k4iznqjz.fsf_-_@jidanni.org> (raw)
In-Reply-To: <b4maajvl6t0.fsf@jpl.org>
>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:
KY> jidanni@jidanni.org wrote:
>> Gentlemen, in http:///jidanni.org/comp/configuration/.gnus.el
>> I do (put 'gnus-summary-edit-article 'disabled t)
>> That works in the *Summary* buffer, but not the *Article* buffer,
>> despite in both places describe-key saying
>> "e runs the command gnus-summary-edit-article".
>> What gives?
>> gnus-version "Gnus v5.13"
KY> The real command that the "e" key is bound to in the article
KY> buffer is `gnus-article-read-summary-keys', which is used to
KY> invoke the summary commands from the article buffer and will
KY> interpret it into:
KY> (call-interactively 'gnus-summary-edit-article)
KY> But it doesn't work for the `disabled' flag as if the command is
KY> actually and directly invoked interactively. I'm not capable to
KY> improve it, sorry.
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!
I also note one sees Describe Key: e-
in the minibuffer, with a "-" added.
Anyway, how can I disable it in the *Article* buffer too?
next prev parent reply other threads:[~2010-12-24 15:22 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 ` jidanni [this message]
2011-01-02 5:58 ` describe-key doesn't tell whole redirect sequence Lars Magne Ingebrigtsen
2011-01-23 0:02 ` bug#7727: " Chong Yidong
2011-01-23 1:19 ` 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=87k4iznqjz.fsf_-_@jidanni.org \
--to=jidanni@jidanni.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=ding@gnus.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).