From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: bug during gnus-summary-move-article
Date: 12 Sep 1998 14:52:44 -400 [thread overview]
Message-ID: <2nyarpcgeb.fsf@zsh.cs.rochester.edu> (raw)
*Symptom: When gnus-summary-copy-article or gnus-summary-move-article
an article with MULTIPART/MIXED, the article in new folder will not be
decoded.
*Reason: The headers of Content-Transfer-Encoding, Content-Type,
Mime-Version are removed by message-remove-header in
message-encode-message-body. The backtrack is
* message-encode-message-body()
gnus-request-accept-article("nnml:test" nil t)
gnus-summary-move-article(nil nil nil copy)
gnus-summary-copy-article(nil)
* call-interactively(gnus-summary-copy-article)
*Rx: Apply this patch
--- gnus-sum.el.orig Sat Sep 12 03:15:36 1998
+++ gnus-sum.el Sat Sep 12 14:44:10 1998
@@ -6920,7 +6920,7 @@
gnus-newsgroup-name)) ; Server
(list 'gnus-request-accept-article
to-newsgroup (list 'quote select-method)
- (not articles)) ; Accept form
+ (not articles) t) ; Accept form
(not articles))) ; Only save nov last time
;; Copy the article.
((eq action 'copy)
@@ -6928,7 +6928,7 @@
(set-buffer copy-buf)
(when (gnus-request-article-this-buffer article gnus-newsgroup-name)
(gnus-request-accept-article
- to-newsgroup select-method (not articles)))))
+ to-newsgroup select-method (not articles) t))))
;; Crosspost the article.
((eq action 'crosspost)
(let ((xref (message-tokenize-header
*Note: Is there a similar bug in gnus-summary-import-article?
--
Shenghuo
next reply other threads:[~1998-09-12 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-12 18:52 Shenghuo ZHU [this message]
1998-09-13 2:53 ` Shenghuo ZHU
1998-09-13 4:00 ` Shenghuo ZHU
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=2nyarpcgeb.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).