Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Cc: bug-gnu-emacs@gnu.org
Subject: Re: bug#7727: describe-key doesn't tell whole redirect sequence
Date: Tue, 25 Jan 2011 01:31:33 -0800	[thread overview]
Message-ID: <87ei81gwi2.fsf@gnus.org> (raw)
In-Reply-To: <jwv62tdn1e6.fsf-monnier+emacs@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> The main benefit is that the keymapping is made clear to describe-key,
> so you wouldn't need gnus-article-describe-key and friends.  Of course,
> all this is hypothetical since we don't have dynamic keymaps.

Sounds good to me.  The `gnus-article-read-summary-keys' thing doesn't
work perfectly anyway, with some prefixed complex key bindings, if I
remember correctly.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      reply	other threads:[~2011-01-25  9:31 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     ` 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 [this message]

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=87ei81gwi2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=ding@gnus.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).