From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/65668 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: [Unicode-2] `read' always returns multibyte symbol Date: Wed, 14 Nov 2007 20:15:37 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1195089363 17879 80.91.229.12 (15 Nov 2007 01:16:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 15 Nov 2007 01:16:03 +0000 (UTC) Cc: Kenichi Handa , ding@gnus.org, emacs-devel@gnu.org To: Katsumi Yamaoka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 15 02:16:07 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 1IsTKs-0006Vq-0X for ged-emacs-devel@m.gmane.org; Thu, 15 Nov 2007 02:16:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IsTKe-0005qa-UW for ged-emacs-devel@m.gmane.org; Wed, 14 Nov 2007 20:15:48 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IsTKb-0005lz-1q for emacs-devel@gnu.org; Wed, 14 Nov 2007 20:15:45 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IsTKV-0005h5-MC for emacs-devel@gnu.org; Wed, 14 Nov 2007 20:15:43 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IsTKV-0005gw-GW for emacs-devel@gnu.org; Wed, 14 Nov 2007 20:15:39 -0500 Original-Received: from tomts43.bellnexxia.net ([209.226.175.110] helo=tomts43-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IsTKV-0004qP-D1 for emacs-devel@gnu.org; Wed, 14 Nov 2007 20:15:39 -0500 Original-Received: from pastel.home ([70.53.194.136]) by tomts43-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20071115011538.TFCB26794.tomts43-srv.bellnexxia.net@pastel.home> for ; Wed, 14 Nov 2007 20:15:38 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 7A3AD7F4E; Wed, 14 Nov 2007 20:15:37 -0500 (EST) In-Reply-To: (Katsumi Yamaoka's message of "Thu, 15 Nov 2007 08:52:57 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) 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:83225 gmane.emacs.gnus.general:65668 Archived-At: >>> ! ;; Use a unibyte buffer in order to make `read' read non-ASCII >>> ! ;; group names (which have been encoded) as unibyte strings. >>> ! (mm-with-unibyte-buffer >>> ! (insert-buffer-substring cur) >> Why is `cur' a multibyte buffer? Since it contains encoded strings, I'd >> expect it would be better (more robust and convenient) to use a unibyte >> buffer for it. > Good point. The `cur' is `nntp-server-buffer' (" *nntpd*") or > `gnus-work-buffer' (" *gnus work*") as the case may be. Don't know about gnus-work-buffer, but nntp-server-buffer should only ever contain unibyte data AFAICT, so it would be better to put it in unibyte mode. > Gnus uses those buffers for various purposes. Although there looks no > situation where it is necessary to have multibyte data as far as I can > observe, Gnus explicitly sets them as multibyte buffers (see > `nnheader-init-server-buffer' and `gnus-set-work-buffer'). > I believe the reason they do so is to prevent from breaking data when > copying them to another multibyte buffer (IIUC, copying data from > a multibyte buffer to a unibyte buffer causes no problem). I'm not sure I understand: copying data from a multibyte buffer to a unibyte buffer is exactly the case that can cause problems. Stefan