From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: saveplace: don't ask for coding system Date: Tue, 04 Dec 2007 06:20:38 +0200 Message-ID: References: <198E2B70-D060-41D8-8BC2-A9614C2729CC@inf.ed.ac.uk> <06675819-C4A8-4D78-AD59-0A2AF296AC7E@inf.ed.ac.uk> <87ve7gn5zc.fsf@red-bean.com> <0CD94276-1D9F-42BB-A6F7-A90ED9E06817@inf.ed.ac.uk> <87bq98n0ka.fsf@red-bean.com> <87fxykjb6y.fsf@red-bean.com> <87hcizihwh.fsf@red-bean.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1196742057 17715 80.91.229.12 (4 Dec 2007 04:20:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Dec 2007 04:20:57 +0000 (UTC) Cc: lekktu@gmail.com, dreitter@inf.ed.ac.uk, emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 04 05:21:04 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IzPHM-0004wf-7X for ged-emacs-devel@m.gmane.org; Tue, 04 Dec 2007 05:21:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IzPH5-0006EH-KQ for ged-emacs-devel@m.gmane.org; Mon, 03 Dec 2007 23:20:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IzPH1-0006Dq-E5 for emacs-devel@gnu.org; Mon, 03 Dec 2007 23:20:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IzPH0-0006DV-3n for emacs-devel@gnu.org; Mon, 03 Dec 2007 23:20:43 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IzPH0-0006DO-0B for emacs-devel@gnu.org; Mon, 03 Dec 2007 23:20:42 -0500 Original-Received: from romy.inter.net.il ([213.8.233.24]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IzPGz-0002yM-Al for emacs-devel@gnu.org; Mon, 03 Dec 2007 23:20:41 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-236-66.inter.net.il [84.228.236.66]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id JNS77877 (AUTH halo1); Tue, 4 Dec 2007 06:20:20 +0200 (IST) In-reply-to: <87hcizihwh.fsf@red-bean.com> (message from Karl Fogel on Mon, 03 Dec 2007 13:32:14 -0800) X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) 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:84629 Archived-At: > Cc: lekktu@gmail.com, dreitter@inf.ed.ac.uk, emacs-devel@gnu.org > From: Karl Fogel > Date: Mon, 03 Dec 2007 13:32:14 -0800 > > The disadvantage is that emacs-mule is Emacs-specific. I don't see this as a big problem in this case: this file is useless for other applications, and almost unreadable by humans. I use this feature all the time, and I only looked at the file perhaps once or twice. It's just a huge Lisp expression. > I've always thought of emacs-mule as a purely internal encoding > system. Yes; and saveplace file is an internal Emacs file, not unlike auto-save files. > If we're starting to push it out to files, that feels a bit > like mission creep to me; it's not a step I'm very comfortable with. I really don't see a rational reason for this uneasiness. emacs-mule is almost iso-2022; would you feel uneasy with that, too? > 1. write it out using utf-8 on the trunk (Emacs 23) line > 2. write it out using emacs-mule on the Emacs 22 line > 3. make sure that saveplace.el reads the coding system from the > first line of the file and uses that to interpret the rest of > the file > > Manual testing just now indicates that ";;; -*- coding: utf-8 -*-" > will look the same (i.e., be the same sequence of bytes) in both > coding systems, and that therefore step (3) above would work. > > Does this seem reasonable to you? Yes. > (I'm not volunteering for (2) or (3), unfortunately. Too bad.