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: One example of code I can't understand Date: Mon, 20 Jul 2009 20:59:41 -0400 Message-ID: References: <833a8soxmc.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1248138006 11730 80.91.229.12 (21 Jul 2009 01:00:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Jul 2009 01:00:06 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 21 02:59:59 2009 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 1MT3i0-00017e-Ef for ged-emacs-devel@m.gmane.org; Tue, 21 Jul 2009 02:59:56 +0200 Original-Received: from localhost ([127.0.0.1]:57870 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MT3hz-0001Cn-Oc for ged-emacs-devel@m.gmane.org; Mon, 20 Jul 2009 20:59:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MT3hv-0001CO-J9 for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:59:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MT3hp-0001B8-5j for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:59:50 -0400 Original-Received: from [199.232.76.173] (port=43276 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MT3hp-0001B5-0t for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:59:45 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:46259) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MT3hl-0004VK-V4; Mon, 20 Jul 2009 20:59:42 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtIEACuwZEpFpZqY/2dsb2JhbACBUM8IhAwFhwI X-IronPort-AV: E=Sophos;i="4.43,237,1246852800"; d="scan'208";a="41928401" Original-Received: from 69-165-154-152.dsl.teksavvy.com (HELO pastel.home) ([69.165.154.152]) by ironport2-out.teksavvy.com with ESMTP; 20 Jul 2009 20:59:41 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 1A0757F66; Mon, 20 Jul 2009 20:59:41 -0400 (EDT) In-Reply-To: (Richard Stallman's message of "Mon, 20 Jul 2009 15:01:48 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:112878 Archived-At: > Why do we need to cater to unibyte operation in Emacs 23? > 1. Unibyte buffers may be needed for certain internal operations. I > am not sure -- we need to ask Handa. Maybe Gnus maintainers would know better (it seems more related to Gnus than to Mule). > 2. As for editing of unibyte buffers by users, maybe nobody will mind > if we get rid of that now. But we should not eliminate it without > first polling the users, to see who uses it and whether it is important. Editing unibyte buffers is an important feature, which we use whenever we edit binary files. I see no need/reason to get rid of it. In this area, there is something that we should eliminate, it's the notion of a unibyte-session (which means something like forcing default-enable-multibyte-characters to t, tho it's a bit trickier than that since default-enable-multibyte-characters is sometimes let-bound around buffer-creation in place of calling set-buffer-multibyte explicitly after the creation). Stefan