From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/63511 Path: news.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.gnus.general Subject: Re: Double Newlines Date: Wed, 26 Jul 2006 17:59:51 -0400 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1154047475 15922 80.91.229.2 (28 Jul 2006 00:44:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 Jul 2006 00:44:35 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+m12037@lists.math.uh.edu Fri Jul 28 02:44:32 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G6GSl-0003fU-04 for ding-account@gmane.org; Fri, 28 Jul 2006 02:44:23 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1G6GSQ-0007r8-00; Thu, 27 Jul 2006 19:44:02 -0500 Original-Received: from nas01.math.uh.edu ([129.7.128.39]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1G5rQb-0006Vh-00 for ding@lists.math.uh.edu; Wed, 26 Jul 2006 17:00:29 -0500 Original-Received: from quimby.gnus.org ([80.91.227.211]) by nas01.math.uh.edu with esmtp (Exim 4.52) id 1G5rQZ-0004Jm-7o for ding@lists.math.uh.edu; Wed, 26 Jul 2006 17:00:29 -0500 Original-Received: from smtp02.lnh.mail.rcn.net ([207.172.157.102]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1G5rQT-0004hn-00 for ; Thu, 27 Jul 2006 00:00:21 +0200 Original-Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 26 Jul 2006 18:00:24 -0400 Original-Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id LYA61497; Wed, 26 Jul 2006 18:00:17 -0400 (EDT) Original-Received: from 216-15-125-177.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com (HELO i9300.luannocracy.com) ([216.15.125.177]) by smtp01.lnh.mail.rcn.net with ESMTP; 26 Jul 2006 18:00:18 -0400 X-IronPort-AV: i="4.07,185,1151899200"; d="scan'208"; a="244234340:sNHT28520148" Original-Received: from dave by i9300.luannocracy.com with local (Exim 4.62) (envelope-from ) id J316FS-000418-62; Wed, 26 Jul 2006 17:59:52 -0400 Original-To: Katsumi Yamaoka In-Reply-To: (Katsumi Yamaoka's message of "Wed, 26 Jul 2006 09:42:48 +0900") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (windows-nt) X-Junkmail-Status: score=10/300, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090202.44C7E336.000A,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.4/2006-05-04 X-Spam-Score: -2.3 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:63511 Archived-At: Katsumi Yamaoka writes: >>>>>> In David Abrahams wrote: > >>> (setq message-send-mail-function >>> (lambda nil >>> (let ((coding-system-for-write 'binary)) >>> (write-region (point-min) (point-max) "~/TESTMAIL")))) >>> >>> What do you see there? > >> This is a test=0D >> This is only a test=0D >> If this had been an actual message, we'd tell you.=0D > >>> If newlines are doubled already, > >> I don't know for sure how to interpret the above, but my first guess >> is that they're not (right?) > > That looks strange to me. `=0D' is the one that the CR character > (0x0d) was encoded by quoted-printable. Rebuilding emacs made that behavior go away (thank you!)... > What does the following > Lisp form return? (To do that, copy it to the *scratch* buffer > and type `C-j' at the end of the last line.) [1] > > (let ((file (make-temp-file "testing")) > (coding-system-for-write 'iso-8859-1) > (coding-system-for-read 'binary)) > (with-temp-file file > (insert "foo\n")) > (prog1 > (with-temp-buffer > (insert-file-contents file) > (buffer-string)) > (delete-file file))) > > If you see > > "foo^M > " > , your Emacs 22 has a bug. Since Kenichi Handa fixed the bug[2] > recently[3], updating your Emacs 22 might fix the problem[4]. ...but curiously, _that_ behavior remains! -- Dave Abrahams Boost Consulting www.boost-consulting.com