From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Should gnus-summary-repair-multipart modify files on disk? (was: New summary part commands?)
Date: Wed, 19 Feb 2003 21:20:18 +0100 [thread overview]
Message-ID: <v9lm0ckoot.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <84of58jdh9.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Wed, 19 Feb 2003 20:07:46 +0100")
On Wed, Feb 19 2003, Kai Großjohann wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>> BTW, for `gnus-summary-repair-multipart' I think we should add a
>> `y-or-no-p' because it may *destroy* an article (on writable back
>> ends), e.g. if the original article wasn't b0rked.
>
> Really? I was shocked, so I quickly scanned the code,
,----[ C-h f gnus-with-article RET ]
| gnus-with-article is a Lisp macro in `gnus-sum'.
| (gnus-with-article ARTICLE &rest FORMS)
|
| Select ARTICLE and perform FORMS in the original article buffer.
| Then replace the article with the result.
`----
Note the last sentence.
> but it appears to only modify the buffer, not the file on disk.
It *does* modify the article disk if you use nnfolder (Article
<news:3D2BFC8C.BeroList-2.5.9@wpxx02.toxi.uni-wuerzburg.de> from
Gmane) copied to nnfolder:Test and `K m'-ed:
--8<---------------cut here---------------start------------->8---
$ diff -U1 multi?.mbox
--- multi1.mbox Wed Feb 19 21:06:34 2003
+++ multi2.mbox Wed Feb 19 21:06:47 2003
[...]
@@ -12,4 +12,2 @@
[...]
-Mime-Version: 1.0
-Content-Type: multipart/signed; micalg=pgp-sha1;
[...]
@@ -40,4 +38,8 @@
[...]
+Mime-Version: 1.0
+Content-Type: multipart/mixed; boundary="mP3DRpeJDSE+ciuQ"
[...]
--8<---------------cut here---------------end--------------->8---
In this case, the repairing was successful. But after reading
<news:m3bs1jppi0.fsf@quimbies.gnus.org>, I did some tests and at least
once, the `repaired' article was corrupt. Maybe I'm able to reproduce
it later. I didn't think that it's a bug, because the user isn't
supposed to `repair' intact articles. ;-)
So the question is: Should gnus-summary-repair-multipart modify files
on disk or only modify the buffer?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-02-19 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 13:39 New summary part commands? Kai Großjohann
2003-02-19 18:12 ` Reiner Steib
2003-02-19 19:07 ` Kai Großjohann
2003-02-19 20:20 ` Reiner Steib [this message]
2003-02-20 11:53 ` Should gnus-summary-repair-multipart modify files on disk? Kai Großjohann
2003-02-19 20:43 ` New summary part commands? Reiner Steib
2003-02-20 10:27 ` Kai Großjohann
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=v9lm0ckoot.fsf_-_@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).