From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: <Multi_key> is undefined
Date: Sun, 23 Mar 2014 09:33:09 +0100 [thread overview]
Message-ID: <8761n5z54q.fsf@fencepost.gnu.org> (raw)
After upgrading to Ubuntu 14.04 (and using Cinnamon), I can no longer
use <Multi_key>. Emacs flashes at me and displays "<Multi_key> is
undefined". This happened with a binary compiled before the upgrade,
and it also happens after I bootstrapped and built Emacs from a clean
directory right now.
The toolkit used is GTK3 (without toolkit scroll-bars, but I should be
surprised if that made a difference).
Any pointers? Using input modes is quite less convenient than relying
on Multi_key for me. What should I be testing? What info might help
further pinpointing this?
I think it's important to get this fixed before the next release. Many
programmers use an American keyboard layout rather than a local one
(because of characters like []{}|) and rely on Multi_key for their
non-English correspondence and text processing.
Now this is clearly related to upgrading the base system, but things
like the terminal window continue working with Multi_key just fine.
--
David Kastrup
next reply other threads:[~2014-03-23 8:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 8:33 David Kastrup [this message]
2014-03-23 8:48 ` <Multi_key> is undefined 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
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=8761n5z54q.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 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).