From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.devel Subject: Re: problem with system_eol_type Date: Tue, 01 Aug 2006 11:03:22 +0900 Organization: Emacsen advocacy group 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 1154397831 6753 80.91.229.2 (1 Aug 2006 02:03:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 1 Aug 2006 02:03:51 +0000 (UTC) Cc: mule-ja@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 01 04:03:49 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G7jbn-0003Bf-LG for ged-emacs-devel@m.gmane.org; Tue, 01 Aug 2006 04:03:48 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7jbn-0005Sk-3b for ged-emacs-devel@m.gmane.org; Mon, 31 Jul 2006 22:03:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G7jba-0005QR-8W for emacs-devel@gnu.org; Mon, 31 Jul 2006 22:03:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G7jbZ-0005Oe-8t for emacs-devel@gnu.org; Mon, 31 Jul 2006 22:03:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7jbZ-0005OU-5x for emacs-devel@gnu.org; Mon, 31 Jul 2006 22:03:33 -0400 Original-Received: from [66.225.201.13] (helo=washington.hostforweb.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1G7jeL-0002K1-TZ for emacs-devel@gnu.org; Mon, 31 Jul 2006 22:06:26 -0400 Original-Received: from [205.234.185.198] (port=34357 helo=mail.jpl.org) by washington.hostforweb.net with esmtpa (Exim 4.52) id 1G7jeN-0006Lz-7Y; Mon, 31 Jul 2006 21:06:27 -0500 Original-To: emacs-devel@gnu.org X-Hashcash: 1:20:060801:emacs-devel@gnu.org::tTvUH/iM+MarXXKh:000000000000000000000000000000000000000000CLdC X-Hashcash: 1:20:060801:mule-ja@m17n.org::ABhPX5lHjECmckC0:03XrF X-Face: #kKnN,xUnmKia.'[pp`; Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu; B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:xV5WDu35agH3FunWrhd+oLOD/nw= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - washington.hostforweb.net X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:57896 Archived-At: ;; Mule-ja people, you can read all the followups at: ;; http://news.gmane.org/group/gmane.emacs.devel/thread=57837/force_load=t >>>>> In Richard Stallman wrote: [...] > I see two possible approaches to this: > 1. Fix those programs to specify `-unix'. That way, they should get > LF eol behavior in all Emacs versions on all systems. > 2. Take out your old change, and implement something at the UI level, > perhaps in a function that reads a coding system name. > #1 is clearly easier. Is there any strong argument against it? I think it is reasonable to use the eol which is system's default when saving text files. Since Gnus uses `raw-text' by default to save files in many cases, mail files, for example, are now saved with CRLF in DOS machines, otherwise with LF. It will be useful when other programs use those files. So, I agree to the recent behavior of Emacs but am negative to change Gnus' default. By the way, why is not CR used in Mac when specifying the coding system `foo', not `foo-eol'? Contrary to this argument concerning saving of files, I hope the forms (encode-coding-string "bar\n" 'foo) and (with-temp-buffer (insert "bar\n") (encode-coding-region (point-min) (point-max) 'foo) (buffer-string)) always return "bar\n" regardless of the system-type in the future as well. I don't have an idea how we should do when communicating with processes. Sorry.