Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: pgnus on a Windows box
Date: 19 Nov 1998 15:29:47 -0500	[thread overview]
Message-ID: <5b67cbs9xg.fsf@ripple.cs.rochester.edu> (raw)
In-Reply-To: Jack Vinson's message of "19 Nov 1998 13:25:20 -0600"

>>>>> "Jack" == Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:

>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>>>>> "Jack" == Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:
Jack> [snip]
Jack> When I open my old archives (from Gnus 5.6.55) pgnus complains.  If I
Jack> look at the file (nnfolder+archive) each line has a Ctrl-M appended
Jack> to the end. 
Jack> [snip]

ZSH> Try (setq nnmail-file-coding-system 'raw-text).

ZSH> But it may lead other errors.

Jack> Yes, it does.  I am not including the backtrace this time, but a different
Jack> error occurs when I use this coding system.  Drat.  

Jack> I've also noticed that old mail messages (nnml) that were saved before the
Jack> transition to Emacs 20.3 are a little strange.  Pgnus is not able to parse
Jack> the header information out of the file.  Actually, it only seems to be the
Jack> code associated with Message.  The summary buffer looks right, but replying
Jack> or following up to a message gives me a message buffer with an empty
Jack> Subject and no To line.  It has no problems with messages that have been
Jack> stored since the arrival of 20.3.

Try this patch and (setq nnmail-file-coding-system 'raw-text). Please
report whether it works or not.

-- 
Shenghuo

:- cut ---------------
--- ChangeLog	1998/11/19 20:22:24	1.1
+++ ChangeLog	1998/11/19 20:26:57
@@ -1,3 +1,9 @@
+Thu Nov 19 15:26:02 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>
+
+	* nnmail.el (nnmail-nov-file-coding-system): New variable.
+	* nnml.el (nnml-open-nov): Use nnmail-nov-file-coding-system.
+	(nnml-save-nov): Use nnmail-nov-file-coding-system.
+
 Thu Nov 19 04:48:42 1998  Lars Magne Ingebrigtsen  <larsi@menja.ifi.uio.no>
 
 	* gnus.el: Pterodactyl Gnus v0.51 is released.

--- nnmail.el	1998/11/19 20:19:49	1.1
+++ nnmail.el	1998/11/19 20:20:20
@@ -496,6 +496,9 @@
 (defvar nnmail-file-coding-system 'binary
   "Coding system used in nnmail.")
 
+(defvar nnmail-nov-file-coding-system 'binary
+  "Coding system used in nov file.")
+
 (defun nnmail-find-file (file)
   "Insert FILE in server buffer safely."
   (set-buffer nntp-server-buffer)

--- nnml.el	1998/11/19 20:16:43	1.1
+++ nnml.el	1998/11/19 20:21:06
@@ -686,7 +686,8 @@
 		       nnml-nov-file-name))
 	  (erase-buffer)
 	  (when (file-exists-p nnml-nov-buffer-file-name)
-	    (nnheader-insert-file-contents nnml-nov-buffer-file-name)))
+	    (let ((nnheader-file-coding-system nnmail-nov-file-coding-system))
+	      (nnheader-insert-file-contents nnml-nov-buffer-file-name))))
 	(push (cons group buffer) nnml-nov-buffer-alist)
 	buffer)))
 
@@ -696,8 +697,9 @@
       (when (buffer-name (cdar nnml-nov-buffer-alist))
 	(set-buffer (cdar nnml-nov-buffer-alist))
 	(when (buffer-modified-p)
-	  (nnmail-write-region 1 (point-max) nnml-nov-buffer-file-name
-			       nil 'nomesg))
+	  (let ((nnmail-file-coding-system nnmail-nov-file-coding-system))
+	    (nnmail-write-region 1 (point-max) nnml-nov-buffer-file-name
+				 nil 'nomesg)))
 	(set-buffer-modified-p nil)
 	(kill-buffer (current-buffer)))
       (setq nnml-nov-buffer-alist (cdr nnml-nov-buffer-alist)))))


  reply	other threads:[~1998-11-19 20:29 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 [this message]
1998-11-20 22:59       ` Jack Vinson
1998-11-24  9:16         ` Shenghuo ZHU
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=5b67cbs9xg.fsf@ripple.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).