unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 23 Nov 2011 11:13:03 +0100	[thread overview]
Message-ID: <1322043183.24352.140661002604425@webmail.messagingengine.com> (raw)
In-Reply-To: <jwv7h2x2uds.fsf-monnier+gnus-read-ephemeral-bug@gnu.org>

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.

Grepping for FRAME_X_XIM doesn't show me where it is supposed to be set,
so I assume the relevant struct member gets assigned directly somewhere.
Where should that be happening?

xim_open_dpy never gets called.
xim_initialize does; dpyinfo->xim is NULL both at the beginning and at
the end of the function.

Any suggestions on where to look next?

Thanks for your time,

-- IDL





  reply	other threads:[~2011-11-23 10:13 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 [this message]
2012-05-13 16:38         ` Ian D. Leroux
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1322043183.24352.140661002604425@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).