From: Klaus Zeitler <kzeitler@lucent.com>
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: 14 Jan 2004 11:46:16 +0100 [thread overview]
Message-ID: <q5gd69mzu2v.fsf@lucent.com> (raw)
In-Reply-To: <CA3682C8-45E5-11D8-8BEE-00039363E640@swipnet.se>
>>>>> "Jan" == Jan D <jan.h.d@swipnet.se> writes:
Jan>
Jan> But is there a reason why XIM is not enabled for you?
>>
>> I have no idea. I only know that XIM exists. I just checked config.h
>> and there's HAVE_XIM and USE_XIM both set to 1. So in theory it should
>> be there. What should I check?
Jan>
Jan> Check if you have HAVE_X_I18N and HAVE_X11R6_XIM defined. The best
Jan> way is to step in xterm.c in the debugger and see why XmbLookupString
Jan> is not called. It may be some problem with creating the XIC or the
Jan> XIM.
sol2.h defines INHIBIT_X11R6_XIM:
--- snip ---
/* inoue@ainet.or.jp says Solaris has a bug related to X11R6-style
XIM support. */
#define INHIBIT_X11R6_XIM
--- snip ---
Thus HAVE_XIM is defined, but HAVE_X11R6_XIM not (see config.h)
just for fun I removed the define for INHIBIT_X11R6_XIM line, but then emacs
crashed in XRegisterIMInstantiateCallback in xim_initialize.
So coming back to the original patch I suggested, maybe we should add it,
but enclosed with e.g. "#ifndef HAVE_X11R6_XIM".
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
One of the lessons of history is that nothing is often a good
thing to do and always a clever thing to say. -- Will Durant
next prev parent reply other threads:[~2004-01-14 10:46 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.
2004-01-12 14:25 ` Klaus Zeitler
2004-01-13 16:30 ` Jan D.
2004-01-14 10:46 ` Klaus Zeitler [this message]
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=q5gd69mzu2v.fsf@lucent.com \
--to=kzeitler@lucent.com \
--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.