From: "Jan D." <jan.h.d@swipnet.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
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 [thread overview]
Message-ID: <384A6738-44F5-11D8-9EE7-00039363E640@swipnet.se> (raw)
In-Reply-To: <q5g8ykdzf3a.fsf@lucent.com>
> 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.
next prev parent reply other threads:[~2004-01-12 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 11:46 [kzeitler@lucent.com: Re: compose key on SUN keyboard creates 2 characters (and beeps)] Richard Stallman
2004-01-12 2:55 ` Jan D.
2004-01-12 9:33 ` Klaus Zeitler
2004-01-12 11:48 ` Jan D. [this message]
2004-01-12 14:25 ` Klaus Zeitler
2004-01-13 16:30 ` Jan D.
2004-01-14 10:46 ` Klaus Zeitler
2004-01-16 10:25 ` Jan D.
2004-01-16 12:57 ` Klaus Zeitler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=384A6738-44F5-11D8-9EE7-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.