From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Post-22.1 development? Date: Sun, 17 Jun 2007 17:49:35 -0400 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1182117189 17782 80.91.229.12 (17 Jun 2007 21:53:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 17 Jun 2007 21:53:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 17 23:53:08 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 1I02gD-0000FQ-4b for ged-emacs-devel@m.gmane.org; Sun, 17 Jun 2007 23:53:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I02gC-0005Ij-PF for ged-emacs-devel@m.gmane.org; Sun, 17 Jun 2007 17:53:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I02cr-0001Uz-2s for emacs-devel@gnu.org; Sun, 17 Jun 2007 17:49:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I02cq-0001UU-Fe for emacs-devel@gnu.org; Sun, 17 Jun 2007 17:49:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I02cq-0001UN-5o for emacs-devel@gnu.org; Sun, 17 Jun 2007 17:49:36 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I02cp-0008C9-NM for emacs-devel@gnu.org; Sun, 17 Jun 2007 17:49:35 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1I02cp-0002vr-A7; Sun, 17 Jun 2007 17:49:35 -0400 In-reply-to: X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:73178 Archived-At: This means that any libraries or other features we might want to add (beyond those "really important") will need to work with unicode-2 Emacs. I know already that some of my own code, which works perfectly well with Emacs 22, will not work as is with unicode-2 Emacs. For example, my code for zooming frames (default font) breaks. We are going to merge unicode-2 pretty soon. Within a few months. Any other feature that we add will have to be adapted, one way or another, to work with unicode-2, by that time. If a feature has conflicts with unicode-2, it makes little sense to rush to install it in the trunk. That would just add to the size of the job of merging the unicode-2 branch. It is much better to adapt the other feature _now_ to work with unicode-2, and install it after that. That way, the work can be done in parallel. You could start doing this now. Meanwhile, if a new feature won't make the unicode-2 merge harder, then we can install it now into the trunk.