From: David Kastrup <dak@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: <Multi_key> is undefined
Date: Sun, 23 Mar 2014 10:52:39 +0100 [thread overview]
Message-ID: <87zjkhjl7c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m24n2pz20o.fsf@linux-m68k.org> (Andreas Schwab's message of "Sun, 23 Mar 2014 10:40:23 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> It's likely not just "my system" but in a month of time the most widely
>> deployed GNU/Linux system.
>
> Any system using ibus (ie. not mine :-) ).
>
>> Can you name a single _other_ application rather than Emacs that should
>> have a non-working Multi_key if "compose handling [was] broken on my
>> system"?
>
> Anything Qt-based.
Nope. Bitcoin-Qt accepts multi_key just fine in its text input boxes.
--
David Kastrup
next prev parent reply other threads:[~2014-03-23 9:52 UTC|newest]
Thread overview: 34+ 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 [this message]
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
2014-03-23 10:16 ` Werner LEMBERG
2014-03-23 13:55 ` Barry Fishman
2014-03-23 12:35 ` Teemu Likonen
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=87zjkhjl7c.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 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).