From: jidanni@jidanni.org
To: tzz@lifelogs.com
Cc: ding@gnus.org
Subject: Re: gnus-mime-*-part vs. the keys they mask
Date: Thu, 16 Oct 2008 05:49:50 +0800 [thread overview]
Message-ID: <87fxmxh6kh.fsf@jidanni.org> (raw)
In-Reply-To: <86k5c9hmuy.fsf@lifelogs.com>
j> p gnus-mime-print-part
TZ> Perhaps it should be 'P'?
But that would mask gnus-summary-prev-article.
p runs the command gnus-mime-print-part
It is bound to p, <menu-bar> <MIME Part> <Print>.
maybe just <menu-bar> <MIME Part> <Print> is enough?
Say, perhaps all the gnus-mime- keys should have their own prefix
keymap, and the more dangerous/conflicting(with the underlying keymap)
ones could be moved there.
TZ> Based on your bug scenarios, you lead a very frustrating life (cf. the
TZ> report in RISKS where you accidentally launched missiles, etc.).
Well at least I haven't started a forest fire, yet.
next prev parent reply other threads:[~2008-10-15 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:18 jidanni
2008-10-15 15:57 ` Ted Zlatanov
2008-10-15 19:58 ` Reiner Steib
2008-10-15 21:49 ` jidanni [this message]
2008-10-16 12:52 ` Ted Zlatanov
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=87fxmxh6kh.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).