From: Matt Christian <mattc@visi.com>
Subject: Re: Rendering on Bm
Date: 20 Aug 2001 18:26:35 -0500 [thread overview]
Message-ID: <87d75qxqhg.fsf@powerhouse.boogie.cx> (raw)
In-Reply-To: <m3d75qmssd.fsf@quimbies.gnus.org>
Hi,
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Karl Kleinpaste <karl@charcoal.com> writes:
>
> > 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)... [...] 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?
>
> Well, you've convinced me. Should I make all the
> moving/copying/re-spooling functions completely non-selecting?
I'm not Karl (or Lars ;) but I'll put my $.02 US in now...
I run into this very same problem when dealing with spam in Gnus. Gnus
attempts to render HTML-based email before completely throwing away the
result and moving the article. I know about the discouraged-alteratives
variables but what spam is actually RFC compliant? I'd rather have
commands like 'B m' just move the dang article without even invoking any
display/rendering routines.
Short answer: yes, could someone please make these functions non-selecting?
- Matt
--
Matt Christian - mattc@visi.com
http://www.visi.com/~mattc/
ftp://ftp.visi.com/users/mattc/
Learn to love and love to learn.
next prev parent reply other threads:[~2001-08-20 23:26 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
2001-08-20 19:32 ` Lars Magne Ingebrigtsen
2001-08-20 23:26 ` Matt Christian [this message]
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=87d75qxqhg.fsf@powerhouse.boogie.cx \
--to=mattc@visi.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).