From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Rendering on Bm
Date: Mon, 20 Aug 2001 15:07:55 -0400 [thread overview]
Message-ID: <vxkbslah7n8.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <m3y9og83na.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 19 Aug 2001 17:34:33 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> All the commands that select an article (and `B m' is one of them)
> renders the article. I don't think it would be appropriate to
> special-case `B m' here.
Considering that the entire `B' keymap consists of actions involving
shuffling things around in the backend (i.e. the filesystem) rather
than the frontend (i.e. my eyeballs)...well, while it may currently
constitute a special case, I don't see any explanation for (what I
perceive as) the failure mode of process-marking 150 messages followed
by `B m' followed by Gnus choking by observing for my "benefit" the
lack of a known PGP key for the signed content therein. I'm moving
the articles Elsewhere -- why should I care about _anything_ having to do
with rendering, least of all the complicated nightmare of invoking PGP?
I've actually developed the tendency to use a keyboard macro when
needing to `B m': The macro begins with `C-u g', so that the article
is pre-rendered in the vacuous sense, followed by `B m' to send it
where it belongs. Being pre-rendered, Gnus doesn't make any further
efforts involving heavyweight foo like PGP. The problem is that I
don't have a way to make a keyboard macro interact with process marks.
next prev parent reply other threads:[~2001-08-20 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 8:53 Graham Murray
2001-08-19 15:34 ` Lars Magne Ingebrigtsen
2001-08-20 17:25 ` Paul Jarc
2001-08-20 19:07 ` Karl Kleinpaste [this message]
2001-08-20 19:32 ` Lars Magne Ingebrigtsen
2001-08-20 23:26 ` Matt Christian
2001-08-21 11:50 ` Per Abrahamsen
2001-08-21 12:05 ` Lars Magne 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=vxkbslah7n8.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).