From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: saveplace: don't ask for coding system Date: Wed, 5 Dec 2007 21:05:39 +0100 Message-ID: References: <198E2B70-D060-41D8-8BC2-A9614C2729CC@inf.ed.ac.uk> <87hcizihwh.fsf@red-bean.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1196885165 20794 80.91.229.12 (5 Dec 2007 20:06:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Dec 2007 20:06:05 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 05 21:06:11 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 1J00VW-0003WR-6K for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2007 21:06:10 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J00VF-0007Z0-Iq for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2007 15:05:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J00V9-0007UX-FV for emacs-devel@gnu.org; Wed, 05 Dec 2007 15:05:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J00V5-0007Nj-2z for emacs-devel@gnu.org; Wed, 05 Dec 2007 15:05:45 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J00V4-0007NH-OA for emacs-devel@gnu.org; Wed, 05 Dec 2007 15:05:42 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.181]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J00V3-0001z6-7I for emacs-devel@gnu.org; Wed, 05 Dec 2007 15:05:41 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so7545904wah for ; Wed, 05 Dec 2007 12:05:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=J2YkNoMCIh/cth7BwPmOEd6+2dXUP0F3k5iF3ld6/PE=; b=aBP7xYGt+sjL3RYVBuOEbbpUv+Hh8dlzCiNdCW2bkokeIVs0F94I0o2cIEnTmXpFcrD85rUlRqmoQbFeyVFWVCkcBVWDWmhcEC/ZQVLzBMqmA3wH5N2CDfFcKmSYyyBT7mzXxeBlGnOpdnNxy3HQE5F0MLPGOuRDO05CwCPcR5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XQnd6H+Ep03QSwHLkuijm+JvVWaLNO2xjaXkf5+7ILrrEPsEc+7zyx67r+EiysjUDGk66G5rm3NQQIBKVjQsXtDs/UIAeCfCpTNjgkpguEb19XK5S0339j5aYWv7TAyESmsRsN/X9+kntU4UxsjhM31QDmXCY2D8FU0//0VP5Nc= Original-Received: by 10.114.184.7 with SMTP id h7mr1286722waf.1196885139412; Wed, 05 Dec 2007 12:05:39 -0800 (PST) Original-Received: by 10.114.170.5 with HTTP; Wed, 5 Dec 2007 12:05:39 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 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:84743 Archived-At: On Dec 5, 2007 7:25 PM, Eli Zaretskii wrote: > Because it wasn't reported by anyone until now, and the current > encoding was in savehist from day one. So IMO this change is not safe > enough and the problem it tries to solve is not important enough to > risk the stability of Emacs 22 branch. Color me puzzled. - The problem has one reporter (me), but so do many other bugs we've been fixing. - The fix is quite simple: changing utf-8 (which is already used by savehist) to utf-8-unix. - The fix affects a file which is only used by Emacs, and in fact, only by the package that creates it. How could that not be "safe enough"? As for "not important", I agree, and moreover, there's an easy workaround (setting savehist-coding-system in your .emacs); so I'm not pushing for fixing in in EMACS_22_BASE. But I honestly don't understand the reticence. Juanma