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: [PATCH] Unicode Lisp reader escapes Date: Mon, 01 May 2006 08:29:30 -0400 Message-ID: <87zmi2apyl.fsf-monnier+emacs@gnu.org> References: <17491.34779.959316.484740@parhasard.net> <17492.29148.246942.842300@parhasard.net> <17493.12935.604847.524198@parhasard.net> <87u08a7c44.fsf@catnip.gol.com> <87hd4acuey.fsf-monnier+emacs@gnu.org> <87y7xm5s4g.fsf@catnip.gol.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1146486599 7238 80.91.229.2 (1 May 2006 12:29:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 May 2006 12:29:59 +0000 (UTC) Cc: Aidan Kehoe , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 01 14:29:56 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FaXXE-0001QT-Pp for ged-emacs-devel@m.gmane.org; Mon, 01 May 2006 14:29:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FaXXE-00089d-9O for ged-emacs-devel@m.gmane.org; Mon, 01 May 2006 08:29:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FaXWy-00089Y-SD for emacs-devel@gnu.org; Mon, 01 May 2006 08:29:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FaXWx-00088v-CK for emacs-devel@gnu.org; Mon, 01 May 2006 08:29:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FaXWx-00088p-34 for emacs-devel@gnu.org; Mon, 01 May 2006 08:29:35 -0400 Original-Received: from [209.226.175.25] (helo=tomts5-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FaXah-00070p-OC; Mon, 01 May 2006 08:33:27 -0400 Original-Received: from alfajor ([70.55.146.223]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060501122930.GARO18394.tomts5-srv.bellnexxia.net@alfajor>; Mon, 1 May 2006 08:29:30 -0400 Original-Received: by alfajor (Postfix, from userid 1000) id 260FDD9211; Mon, 1 May 2006 08:29:30 -0400 (EDT) Original-To: Miles Bader In-Reply-To: <87y7xm5s4g.fsf@catnip.gol.com> (Miles Bader's message of "Mon, 01 May 2006 12:41:19 +0900") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:53717 Archived-At: >> Currently The syntax for \xNNNN hexadeciaml escapes is that it ends whenever >> reaching a non-hexadecimal char, and if you need your \xNNN escape to be >> followed by an hexidecimal char, then you have to seprate the two with "\ " >> (and the Lisp printer does that automatically, of course). >> Is there a strong reason not do use the same rule for \u ? > That might be sufficient for programmatic output, but anything involving > a significant space seems problematic in general... Sorry, I don't understand what you mean by "significant space". Stefan