From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: Re: pgnus on a Windows box
Date: 25 Nov 1998 08:51:22 -0600 [thread overview]
Message-ID: <wk1zmromfp.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Shenghuo ZHU's message of "Tue, 24 Nov 1998 04:16:19 -0500"
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
Jack> * Message doesn't quite understand mail saved before I upgraded
Jack> to 20.3. When I reply to older mail, message is unable to find
Jack> the author and subject. The summary buffer displays this
Jack> information with no problem.
ZSH> Weird. If possible, could you send a (encoded) sample?
Sure, I can try. The problem is completely solved if I do
(setq nnmail-file-coding-system 'raw-text-dos)
But the example is pretty straightforward. With this value set to 'binary,
my summary buffer looks normal. As shown in the enclosed ex_summary.txt.
(All of these messages happen to have come before I moved to emacs-20.3.1.)
When I hit reply on a message, the message buffer looks like
ex_message1.txt. If I change nnmail-file-coding-system to 'raw-text-dos
and reply to the same message, the message buffer looks correct as shown in
ex_message2.txt. For this to work I must select a different message and
then reselect the first message for the nnmail-file-coding-system to take
effect when it reads that file. (I am working in the nnml back end.)
I have also set
(setq nnheader-file-coding-system 'no-conversion)
[-- Attachment #2: Type: text/plain, Size: 699 bytes --]
! [ 232: *Onsale Auto Reply ] Congratulations! Your bid #5137130 was successful.
O [ 80: *Onsale Auto Reply ] Your recent bid has been reinstated as a currently winning bid
! [ 216: *Onsale Auto Reply ] Congratulations! Your bid #5154369 was successful.
! [ 182: *Onsale Auto Reply ] Your Bid #5438668 received
! [ 206: *Onsale Auto Reply ] Congratulations! Your bid #5438668 was successful.
E [ 43: *Onsale Maillist ] New at ONSALE - Expanded Quick Buy
E [ 61: *Onsale Maillist ] Weekend Monitor Madness with bids starting at $1
E [ 59: *Onsale Maillist ] Sony Hi Res Advanced Digital Camera starts @ $1
E [ 66: *Onsale Maillist ] 11 ProForm Treadmills starting @ $1
[-- Attachment #3: Type: text/plain, Size: 116 bytes --]
Subject: Re: none
Gcc: nnfolder+archive:misc-mail
X-Zippy: Look DEEP into the OPENINGS!!
--text follows this line--
[-- Attachment #4: Type: text/plain, Size: 240 bytes --]
To: ONSALE <Onsale_Maillist@new-jersey.onsale.com>
Subject: Re: Weekend Monitor Madness with bids starting at $1
References: <199810162354.TAA22916@unagi.cis.upenn.edu>
Gcc: nnfolder+archive:misc-mail
X-Zippy: ..
--text follows this line--
[-- Attachment #5: Type: text/plain, Size: 111 bytes --]
--
Jack Vinson <jvinson@chevax.ecs.umass.edu> http://www.cis.upenn.edu/~vinson/
Zippy: My EARS are GONE!!
next prev parent reply other threads:[~1998-11-25 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-19 15:41 Jack Vinson
1998-11-19 18:39 ` Shenghuo ZHU
1998-11-19 19:25 ` Jack Vinson
1998-11-19 20:29 ` Shenghuo ZHU
1998-11-20 22:59 ` Jack Vinson
1998-11-24 9:16 ` Shenghuo ZHU
1998-11-25 14:51 ` Jack Vinson [this message]
1998-11-29 10:10 ` Shenghuo ZHU
1998-12-03 17:00 ` Jack Vinson
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=wk1zmromfp.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.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).