From: "Ian D. Leroux" <idleroux@fastmail.fm>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7380@debbugs.gnu.org
Subject: bug#7380: 23.2; Dead keys misinterpreted in gtk emacs
Date: Sun, 13 May 2012 18:38:05 +0200 [thread overview]
Message-ID: <1336927085.18509.140661074920597.650DEE80@webmail.messagingengine.com> (raw)
In-Reply-To: <1322043183.24352.140661002604425@webmail.messagingengine.com>
On Wed, Nov 23, 2011, at 11:13, Ian D. Leroux wrote:
> On Friday, November 18, 2011 1:03 PM, "Stefan Monnier"
> <monnier@iro.umontreal.ca> wrote:
> > > Where is FRAME_XIC (f) supposed to be set?
> >
> > In the x_window function, in src/xfns.c (there are 3 versions of
> > this function :-( depending on whether or not we're using Gtk or
> > some other toolkit or no toolkit at all).
> >
> > Could it be that use_xim is 0, somehow?
>
> use_xim is 1, but FRAME_X_XIM (f) is NULL when create_frame_xic is
> called. As a result, the "if(xim)" test at line 2315 in xfns.c fails,
> xic does not get allocated, and FRAME_XIC(f) remains NULL at the end
> of the function.
The problem has now been identified: due to a configuration error in the
en_US.UTF-8 locale settings in NetBSD's default xorg installation,
libX11 was not loading the new callback based XIM apis. Most software
was falling back to the older open/close api, and thus continuing to
support dead keys, while emacs gave up on XIM entirely and fell back to
XLookupString. As far as I'm concerned, this bug can now be closed.
-- IDL
next prev parent reply other threads:[~2012-05-13 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 23:18 bug#7380: 23.2; Dead keys misinterpreted in gtk emacs Ian D. Leroux
2010-11-16 16:57 ` Stefan Monnier
2010-11-16 23:56 ` Ian D. Leroux
2010-11-21 0:31 ` Ian D. Leroux
2011-11-18 18:03 ` Stefan Monnier
2011-11-23 10:13 ` Ian D. Leroux
2012-05-13 16:38 ` Ian D. Leroux [this message]
2012-05-14 17:26 ` Glenn Morris
2011-11-14 21:02 ` bug#7380: Dead keys bug, additional info Ian D. Leroux
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=1336927085.18509.140661074920597.650DEE80@webmail.messagingengine.com \
--to=idleroux@fastmail.fm \
--cc=7380@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.