From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: gnus-summary-repair-multipart (K m) not working in nndoc
Date: 02 Dec 1998 22:50:48 +0300 [thread overview]
Message-ID: <m33e6yb9wn.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Dec 1998 23:57:47 +0100"
"LMI" == Lars Magne Ingebrigtsen writes:
>> when i try to `repair' messages in nndoc (after pressing C-d on a
>> digest message) i get an error:
LMI> Yup. Fix in Pterodactyl Gnus v0.59.
Well. The current implementation of gnus-summary-repair-multipart
seems to be not 100% safe, because it only looks for "\n--" to find a
part boundary. So, it can easily break the message by treating e.g. a
signature beginning as a MIME boundary. IMHO, one should at least do
something like (looking-at "[\41-\176]+$") [or whatever is an allowed
characters for boundary], and also, even better, to make reparing only
if there is a line "^--boundary--$", too.
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.
Best regards, -- Vladimir.
next prev parent reply other threads:[~1998-12-02 19:50 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 [this message]
1998-12-02 22:31 ` 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=m33e6yb9wn.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).