From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: jidanni@jidanni.org, 7727-close@debbugs.gnu.org,
yamaoka@jpl.org, bug-gnu-emacs@gnu.org, ding@gnus.org
Subject: Re: bug#7727: describe-key doesn't tell whole redirect sequence
Date: Mon, 24 Jan 2011 14:01:36 -0800 [thread overview]
Message-ID: <87aaiqota7.fsf@gnus.org> (raw)
In-Reply-To: <jwvwrlunu5n.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 24 Jan 2011 11:31:31 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> A cleaner could look like the following: add dynamic keymaps to Emacs,
> where "dynamic keymaps" are represented as functions/objects a bit like
> functional completion tables.
Hm... how would that work?
The complicated run-summary-commands-from-the-article-buffer thing is
quite, er, complicated, because some commands need to keep the window
conf, while others shouldn't, and stuff.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-24 22:01 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 [this message]
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=87aaiqota7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=7727-close@debbugs.gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.org \
--cc=monnier@iro.umontreal.ca \
--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).