From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: <Multi_key> is undefined
Date: Sun, 23 Mar 2014 14:44:14 +0100 [thread overview]
Message-ID: <874n2pyqq9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 532EB6AE.8050803@dancol.org
Daniel Colascione <dancol@dancol.org> writes:
> On 03/23/2014 03:16 AM, Daniel Colascione wrote:
>> On 03/23/2014 03:08 AM, Daniel Colascione wrote:
>>> On 03/23/2014 02:56 AM, Andreas Schwab wrote:
>>>> David Kastrup <dak@gnu.org> writes:
>>>>
>>>>> Nope. Bitcoin-Qt accepts multi_key just fine in its text input boxes.
>>>>
>>>> Does it use Qt for its input box?
>>>
>>> Works fine for me with qgit in a normal Qt input box. nedit breaks the
>>> same way Emacs does, though.
>>>
>>> I did a bit of debugging. xterm works fine; it's using
>>> Xutf8LookupString/XmbLookupString, depending on wide character mode.
>>> Emacs has code to call XmbLookupString, but it's not being run because
>>> FRAME_XIC ends up being NULL. No idea why yet.
>>
>> Found it. Emacs' XCreateIC is failing because we pass an
>> XNStatusAttributes; omitting this parameter makes the compose system
>> work fine. Let me see whether omitting this parameter has any side
>> effects; if it doesn't, I'll check in a patch to retry XCreateIC without
>> XNStatusAttributes if the first call fails.
>
> I pushed a fix to trunk. Can you please try it now? Compose works for me
> without having to muck with XMODIFIERS.
There is a short bug fix branch merged into trunk twice (first merge
integrating two commits, second merge integrating another two). For me,
the Compose key problem is already fixed with the first of those merge
commits. I have verified that the problem is still present immediately
before the first merge commit.
Thanks!
--
David Kastrup
next prev parent reply other threads:[~2014-03-23 13:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 8:33 <Multi_key> is undefined David Kastrup
2014-03-23 8:48 ` Andreas Schwab
2014-03-23 9:17 ` David Kastrup
2014-03-23 9:20 ` Daniel Colascione
2014-03-23 9:29 ` David Kastrup
2014-03-23 16:14 ` Eli Zaretskii
2014-03-23 16:22 ` David Kastrup
2014-03-23 16:47 ` Eli Zaretskii
2014-03-23 17:50 ` Werner LEMBERG
2014-03-23 18:15 ` David Kastrup
2014-03-23 10:21 ` Eric Abrahamsen
2014-03-23 13:20 ` David Kastrup
2014-03-23 9:20 ` David Kastrup
2014-03-23 9:40 ` Andreas Schwab
2014-03-23 9:52 ` David Kastrup
2014-03-23 9:56 ` Andreas Schwab
2014-03-23 10:08 ` Daniel Colascione
2014-03-23 10:16 ` Daniel Colascione
2014-03-23 10:23 ` Werner LEMBERG
2014-03-23 10:25 ` Daniel Colascione
2014-03-23 11:37 ` Werner LEMBERG
2014-03-23 11:39 ` Daniel Colascione
2014-03-23 11:44 ` Werner LEMBERG
2014-03-23 11:50 ` Daniel Colascione
2014-03-23 11:57 ` Werner LEMBERG
2014-03-23 12:10 ` Daniel Colascione
2014-03-23 14:33 ` Barry Fishman
2014-03-23 14:46 ` Daniel Colascione
2014-03-23 19:36 ` Barry Fishman
2014-03-24 1:40 ` Stephen J. Turnbull
2014-03-23 13:44 ` David Kastrup [this message]
2014-03-23 10:16 ` Werner LEMBERG
2014-03-23 13:55 ` Barry Fishman
2014-03-23 12:35 ` Teemu Likonen
-- strict thread matches above, loose matches on Subject: below --
2015-04-08 14:06 jonetsu
[not found] <mailman.208.1428504833.904.help-gnu-emacs@gnu.org>
2015-04-08 17:21 ` Emanuel Berg
2015-04-08 18:59 ` Re[2]: " jonetsu
2015-04-09 0:44 ` Stefan Monnier
[not found] ` <mailman.230.1428519467.904.help-gnu-emacs@gnu.org>
2015-04-09 2:57 ` Re[2]: " Rusi
2015-04-09 19:53 ` Re[4]: " jonetsu
2015-04-10 2:49 ` Eric Abrahamsen
[not found] ` <mailman.329.1428609127.904.help-gnu-emacs@gnu.org>
2015-04-10 16:20 ` Re[4]: " Rusi
2015-04-10 17:37 ` Stefan Monnier
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=874n2pyqq9.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@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.