From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David De La Harpe Golden Newsgroups: gmane.emacs.devel Subject: Re: inputting characters by hexadigit Date: Fri, 18 Jul 2008 18:33:24 +0100 Message-ID: <4880D3E4.7050400@harpegolden.net> References: <868ww3vydn.fsf@lifelogs.com> <87myki6fqp.fsf@jurta.org> <87mykhz6tf.fsf@jurta.org> <87tzeokrku.fsf@jurta.org> <87tzeogih6.fsf@catnip.gol.com> <488020A4.4060601@harpegolden.net> <87vdz3p3om.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1216402440 9384 80.91.229.12 (18 Jul 2008 17:34:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Jul 2008 17:34:00 +0000 (UTC) Cc: juri@jurta.org, tzz@lifelogs.com, emacs-devel@gnu.org, Kenichi Handa , Miles Bader To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 18 19:34:47 2008 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 1KJtqw-0003H9-4T for ged-emacs-devel@m.gmane.org; Fri, 18 Jul 2008 19:34:46 +0200 Original-Received: from localhost ([127.0.0.1]:48323 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KJtq3-0008UB-8r for ged-emacs-devel@m.gmane.org; Fri, 18 Jul 2008 13:33:51 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KJtpw-0008SK-Co for emacs-devel@gnu.org; Fri, 18 Jul 2008 13:33:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KJtpt-0008Ok-GJ for emacs-devel@gnu.org; Fri, 18 Jul 2008 13:33:42 -0400 Original-Received: from [199.232.76.173] (port=52692 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KJtpt-0008OX-Bu for emacs-devel@gnu.org; Fri, 18 Jul 2008 13:33:41 -0400 Original-Received: from harpegolden.net ([65.99.215.13]:56221) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KJtpn-0004Fq-9P; Fri, 18 Jul 2008 13:33:35 -0400 Original-Received: from golden1.harpegolden.net (86-43-171-96.b-ras2.prp.dublin.eircom.net [86.43.171.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "David De La Harpe Golden", Issuer "David De La Harpe Golden Personal CA rev 3" (verified OK)) by harpegolden.net (Postfix) with ESMTP id DA26C8115; Fri, 18 Jul 2008 17:33:32 +0000 (UTC) User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) In-Reply-To: <87vdz3p3om.fsf@uwakimon.sk.tsukuba.ac.jp> X-Enigmail-Version: 0.95.0 X-detected-kernel: by monty-python.gnu.org: 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:100949 Archived-At: Stephen J. Turnbull wrote: > > Yes, that sounds like a good syntax to me -- I think it's important that > > it be easy to remember, because many people will use it only > > occasionally. > > Agreed, but how about trying the syntax everybody actually uses: `C-q > U+00C0'? Well, quibbling, but not sure that everybody uses that for _input_. Gtk+/GOME apps, firefox use C-s-U 00C0 for example (yes I know that's not a runner for emacs, where C-u, sometimes indistinguishable from C-s-U, is already an important keypress). More importantly: Does C-q still do language-environment based translations for octal input #o200 -> #o377 ? Manual node "Inserting Text" says it does, but it doesn't seem to be doing quite what it says I'm not 100% on what it is doing - embedding the raw byte? Funny thing is e.g. C-q 23030 embeds U+2618 as expected. I was, not necessarily for any particularly good reason, thinking that entering C-q #xnumber-in-hexadecimal would always do _exactly_ what the same C-q number-in-octal does ( in turn same as C-q number-in-hexadecimal with a hex read-quoted-char-radix). => If translations as documented in the manual are happening, that would mean that number is _not_ necessarily simply a unicode code and C-q U+ could be misleading. OTOH,if it departed from that C-q octal behaviour and _always_ inserted the _unicode_ char, well, then C-q U+ would seem fairly appropriate.