From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze on October 1 Date: Tue, 25 Sep 2012 09:12:44 -0400 Message-ID: References: <87haqp1okn.fsf@gnu.org> <83zk4fiiw9.fsf@gnu.org> <837griinsy.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348578804 7887 80.91.229.3 (25 Sep 2012 13:13:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Sep 2012 13:13:24 +0000 (UTC) Cc: handa@gnu.org, cyd@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 25 15:13:28 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TGUx3-0003uG-Fq for ged-emacs-devel@m.gmane.org; Tue, 25 Sep 2012 15:13:25 +0200 Original-Received: from localhost ([::1]:51334 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGUwy-0005Pa-AK for ged-emacs-devel@m.gmane.org; Tue, 25 Sep 2012 09:13:20 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:34191) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGUwr-0005OH-IJ for emacs-devel@gnu.org; Tue, 25 Sep 2012 09:13:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TGUwi-0007Pj-6S for emacs-devel@gnu.org; Tue, 25 Sep 2012 09:13:13 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:51452) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGUwX-0007OV-0O; Tue, 25 Sep 2012 09:12:53 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAG6Zu09FpZV1/2dsb2JhbABEtBGBCIIVAQEEAVYjBQsLNBIUGA0kiBwFugmQRAOjM4FYgwU X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="199922597" Original-Received: from 69-165-149-117.dsl.teksavvy.com (HELO pastel.home) ([69.165.149.117]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 25 Sep 2012 09:12:44 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 7099E593DE; Tue, 25 Sep 2012 09:12:44 -0400 (EDT) In-Reply-To: <837griinsy.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Sep 2012 09:06:37 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153532 Archived-At: > Should we also remove MAYBE_UNIFY_CHAR and maybe_unify_char as well? I think so, yes. > And what about CHAR_STRING_ADVANCE_NO_UNIFY and > STRING_CHAR_ADVANCE_NO_UNIFY? Should we remove them and use, > respectively, CHAR_STRING_ADVANCE and STRING_CHAR_ADVANCE instead? Yes. > Or do we want to leave all these in place for now, to keep the option > of going back to using the unification in some cases? We have the Bazaar history for that. Stefan