From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-summary-repair-multipart (K m) not working in nndoc
Date: 02 Dec 1998 23:31:28 +0100 [thread overview]
Message-ID: <m3ogpmnpkv.fsf@sparky.gnus.org> (raw)
In-Reply-To: Vladimir Volovich's message of "02 Dec 1998 22:50:48 +0300"
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> I'd also be happy if gnus-summary-repair-multipart could be made
> `non-destructive', i.e. only `repair' in the memory while viewing, but
> not replacing the message, so that one could safely put it into, say,
> message-prepare-hook.
No, you'd never be able to do that. The command is supposed to make
Gnus understand messages that have been destroyed during transport.
There may be only one thing that looks like a boundary, and the
command has to guess. There's no way to make it safe.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-12-02 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-01 9:33 Vladimir Volovich
[not found] ` <6femqkrsqh.fsf@dna.lth.se>
1998-12-01 13:14 ` Vladimir Volovich
1998-12-01 22:57 ` Lars Magne Ingebrigtsen
1998-12-02 19:50 ` Vladimir Volovich
1998-12-02 22:31 ` Lars Magne 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=m3ogpmnpkv.fsf@sparky.gnus.org \
--to=larsi@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).