From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: pgnus on a Windows box
Date: 24 Nov 1998 04:16:19 -0500 [thread overview]
Message-ID: <2nogpxxxgc.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: Jack Vinson's message of "Fri, 20 Nov 1998 23:01:27 GMT"
>>>>> "Jack" == Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:
>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
ZSH> Try this patch and (setq nnmail-file-coding-system 'raw-text). Please
ZSH> report whether it works or not.
Jack> The patch Shenghou created didn't help. The problem is
Jack> obviously the coding system. I tried 'raw-text-dos (as opposed
Jack> to 'raw-text) with the original files and that seemed to do the
It is weird. raw-text should be equivalent to raw-text-dos in NTEmacs.
Maybe it is a bug in NTEmacs.
DOC> t -- raw-text
DOC> Raw text, which means text contains random 8-bit codes.
DOC> Type: 5 (text with random binary characters)
DOC> EOL type: Automatic selection from:
DOC> [raw-text-unix raw-text-dos raw-text-mac]
DOC> This coding system can encode charsets:
Jack> trick. To read my nnfolders I had to only set
Jack> nnheader-file-coding-system.
It seems that gnus needs more coding-system variables. Each backend
needs a file-coding-system and path-coding-system, since backends may
locate on different file systems and share with other os.
Jack> There are other problems:
Jack> * drafts get saved with the and Gnus forgets to ignore them when
Jack> loading the file. I need to set nnmail-file-coding-system to
Jack> 'raw-text-dos to get this right.
Could you test my patch in "PATCH: more charset"? And remember to set
"charset" to "nil" in nndraft:drafts ( `G c' on nndraft:drafts) or
delete (`C-k') it and gnus will recreate it next time.
Jack> * MIME binary parts (jpeg & gif) are getting saved with trailing
Jack> 's and I can't view the image. It looks like the
Jack> buffer-file-coding-system is getting set to 'undecided-dos which
Jack> happens to be the default-buffer-file-coding-system.
Could you test my patch in "Re: MIME decoding broken on Win NT"?
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.
Weird. If possible, could you send a (encoded) sample?
--
Shenghuo
next prev parent reply other threads:[~1998-11-24 9:16 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 [this message]
1998-11-25 14:51 ` Jack Vinson
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=2nogpxxxgc.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).