From mboxrd@z Thu Jan 1 00:00:00 1970 Path: quimby.gnus.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: ChangeLog and unification Date: Wed, 20 Feb 2002 08:27:43 +0200 (IST) Message-ID: NNTP-Posting-Host: quimby2.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: quimby2.netfonds.no 1014186647 29052 195.204.10.66 (20 Feb 2002 06:30:47 GMT) X-Complaints-To: usenet@quimby2.netfonds.no NNTP-Posting-Date: 20 Feb 2002 06:30:47 GMT Cc: monnier+gnu/emacs@RUM.cs.yale.edu, Kai.Grossjohann@CS.Uni-Dortmund.DE, schwab@suse.de, emacs-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby2.netfonds.no with esmtp (Exim 3.12 #1 (Debian)) id 16dQH8-0007YU-00 for ; Wed, 20 Feb 2002 07:30:46 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16dQGf-000730-00; Wed, 20 Feb 2002 01:30:17 -0500 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16dQEy-0006s6-00; Wed, 20 Feb 2002 01:28:32 -0500 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id IAA21800; Wed, 20 Feb 2002 08:27:44 +0200 (IST) X-Sender: eliz@is Original-To: Richard Stallman In-Reply-To: <200202192131.g1JLV8813172@aztec.santafe.edu> Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: quimby.gnus.org gmane.emacs.devel:1354 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:1354 On Tue, 19 Feb 2002, Richard Stallman wrote: > I really think unify-on-encode should be turned ON by default > because I still haven't heard of any reasonable scenario where it can > do anything undesirable. > > Does anyone see a reason not to do this? We could certainly try doing so in the CVS version. If there are downsides to this, that would be a good way of exposing them. Then we'd have enough data points to make the decision when Emacs 21.3 will go into pretest. _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://mail.gnu.org/mailman/listinfo/emacs-devel