From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: [kzeitler@lucent.com: Re: compose key on SUN keyboard creates 2 characters (and beeps)] Date: Mon, 12 Jan 2004 12:48:20 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <384A6738-44F5-11D8-9EE7-00039363E640@swipnet.se> References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1073910514 31947 80.91.224.253 (12 Jan 2004 12:28:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Jan 2004 12:28:34 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jan 12 13:28:15 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ag1B1-0004mB-00 for ; Mon, 12 Jan 2004 13:28:15 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ag1B1-000475-00 for ; Mon, 12 Jan 2004 13:28:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Ag1YR-00043C-NI for emacs-devel@quimby.gnus.org; Mon, 12 Jan 2004 07:52:27 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1Ag1Xh-0003zo-2Z for emacs-devel@gnu.org; Mon, 12 Jan 2004 07:51:41 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1Ag1Wy-0003qW-HB for emacs-devel@gnu.org; Mon, 12 Jan 2004 07:51:27 -0500 Original-Received: from [193.201.16.94] (helo=stubby.bodenonline.com) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Ag1Wx-0003qD-PX; Mon, 12 Jan 2004 07:50:55 -0500 Original-Received: from accessno42.bodenonline.com (accessno42.bodenonline.com [193.201.16.44]) by stubby.bodenonline.com (8.12.1/8.12.1) with ESMTP id i0CCg4wq032486; Mon, 12 Jan 2004 13:42:06 +0100 In-Reply-To: Original-To: Klaus Zeitler X-Mailer: Apple Mail (2.609) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:19142 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19142 > Jan> check for > 0 (no need to limit ourselves to 1 or 2) can be > done. But > > are you sure, this would amaze me? I thought when chars_matched is 3, > emacs > needs to handle the char, and as long as we're composing a character, > we need > to ignore it. I would expect chars_matched to be set to 0 when a complete character has been composed. But this may not be so, it all depends on what Sun has done. > Does the compose key work the way it's implemented now e.g. under > GNU/Linux? Compose processing works with XIM/XIC, so XLookupString is never called. But if you turn XIM off (emacs --xrm '*useXIM: false') it does not work. Nor can it be made to work in Emacs, since the code in XLookupString that did compose processing has been conditionalized out in XFree86. The compose_status parameter is never modifyed by XLookupString by XFree86. It sounds as if Sun is doing something else, I'll try to figure out what when I can get my hand on a Solaris machine. But is there a reason why XIM is not enabled for you? Jan D.