Gnus development mailing list
 help / color / mirror / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: xemacs-beta@xemacs.org
Subject: Re: Bug in gnus/uudecode.el
Date: Tue, 22 Mar 2005 23:55:46 +0900	[thread overview]
Message-ID: <87k6nzspal.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <v9d5trzyt5.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 22 Mar 2005 12:48:22 +0100")

>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

    >> No, it's a bug in the uudecode library in Gnus, which assumes
    >> that 'nil is always a valid coding system pair.  In XEmacs it
    >> isn't.

    Reiner> Could you be more specific (which function, ...) and maybe
    Reiner> provide a patch making it compatible with XEmacs, please?

*sigh* I hate doing this---I don't have very good reason to suppose
this will work for anyone but me---but I don't have time to do it
right.  Here's a patch against current XEmacs package CVS, but it
should be pretty close for this ancient protocol.

Index: lisp/uudecode.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/gnus/lisp/uudecode.el,v
retrieving revision 1.3
diff -u -p -r1.3 uudecode.el
--- lisp/uudecode.el	28 Sep 2004 02:21:21 -0000	1.3
+++ lisp/uudecode.el	22 Mar 2005 14:51:09 -0000
@@ -99,7 +99,7 @@ (defun uudecode-decode-region-external
 			      (make-temp-name "uu")
 			      uudecode-temporary-file-directory))))
 	(let ((cdir default-directory)
-	      default-process-coding-system)
+	      (default-process-coding-system '(binary . binary)))
 	  (unwind-protect
 	      (with-temp-buffer
 		(insert "begin 600 " (file-name-nondirectory tempfile) "\n")



-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.



      reply	other threads:[~2005-03-22 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ad610dceaf0159c66422b9fff5ee85ce@siru.org>
     [not found] ` <r7iap69b.fsf@smtprelay.t-online.de>
     [not found]   ` <acoyp5xh.fsf@smtprelay.t-online.de>
     [not found]     ` <15e6f5b15d94c65b9e3a05c698edf628@siru.org>
     [not found]       ` <87is3k70im.fsf@tleepslib.sk.tsukuba.ac.jp>
2005-03-22 11:48         ` Bug in gnus/uudecode.el (was: Possible bug in TRAMP?) Reiner Steib
2005-03-22 14:55           ` Stephen J. Turnbull [this message]

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=87k6nzspal.fsf@tleepslib.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=xemacs-beta@xemacs.org \
    /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).