From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Barry Fishman <barry_fishman@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: <Multi_key> is undefined
Date: Mon, 24 Mar 2014 10:40:31 +0900 [thread overview]
Message-ID: <8738i8idbk.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <m3wqfkbtce.fsf@barry_fishman.acm.org>
Barry Fishman writes:
> But that environment does not work.
True, for the moment.
> If the choice is to figure out how to modify your environment
> variables before entering Emacs, or have Emacs just work, I choose
> the latter.
Unfortunately, that is not the choice. We have no choice but to
prepare to defend ourselves for some time: we are under attack by the
slings and arrows of outrageous IM developers.
For reasons I don't understand, the Linux[1], X11, and generic-IM
communities have chosen to repeatedly change keyboard handling in
backward-incompatible ways. From what I hear from Ubuntu users, at
least generic-IM still doesn't have it right. So we may suffer
another such attack in the not so distant future (due to what Jamie
calls the "CADT syndrome" <URL:http://www.jwz.org/doc/cadt.html>).
> Either way it is a gross hack.
Precisely. If you have an up-to-date environment, a patched Emacs
will work without the hack. This *should* remain true indefinitely,
modulo the aforementioned slings and arrows. There's no guarantee
with the hack, and the hack *will* break something else for some
people.
Footnotes:
[1] If you're Gibozing, Richard, indeed I do mean the kernel
development community.
next prev parent reply other threads:[~2014-03-24 1:40 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
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 [this message]
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=8738i8idbk.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=barry_fishman@acm.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).