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: Tue, 16 Nov 2010 18:56:30 -0500 [thread overview]
Message-ID: <1289951790.6461.1405669531@webmail.messagingengine.com> (raw)
In-Reply-To: <jwvd3q5z0qq.fsf-monnier+emacs@gnu.org>
On Tue, 16 Nov 2010 11:57 -0500, "Stefan Monnier"
<monnier@IRO.UMontreal.CA> wrote:
> Now, as to why this X11 key composition does not work for you. Could
> you maybe try to rebuild it and show us the output of "configure"? Not
> sure it'll help, tho. We'll need either someone to be able to
> reproduce it, or you'll need to dig in the code, play with GDB to try
> and see what's going on there. If you're up to it, you can try and
> place breakpoints near the call to XmbLookupString in xterm.c and
> single step there. Normally, the dead-acute event should not escape
> from this part of the code: instead it should turn into "nothing"
> (just change some state somewhere either in compose_status or in
> "FRAME_XIC (f)" depending on whether that frame uses XIM/XIC), and
> subsequent "e" should in that same part of the code be turned into an
> "é" (so the Elisp code never even gets to know that this é was input
> as two separate key presses).
Thanks for the pointers. I'll rebuild and poke around in gdb as you
suggest later in the week and report back any interesting findings.
Thanks for your assistance,
Ian Leroux
next prev parent reply other threads:[~2010-11-16 23:56 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 [this message]
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
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=1289951790.6461.1405669531@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.