From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: <Multi_key> does not work anymore
Date: Wed, 11 Mar 2015 01:35:18 +0100 [thread overview]
Message-ID: <87pp8g1id5.fsf@debian.uxu> (raw)
In-Reply-To: 87mw3k3dkg.fsf@Equus.decebal.nl
Cecil Westerhof <Cecil@decebal.nl> writes:
> Because <Multi_key> is the start of a very big range
> of conversion. I would not want to define them all
> by hand.
Why not? :)
> Problem is (probably) solved with: /usr/bin/env -u
> XMODIFIERS /usr/bin/emacs
Probably a good idea is to write a mail to the people
maintaining the software which you upgraded if they
are unaware of this side-effect.
--
underground experts united
prev parent reply other threads:[~2015-03-11 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 21:06 <Multi_key> does not work anymore Cecil Westerhof
2015-03-05 22:12 ` Cecil Westerhof
2015-03-06 0:02 ` Emanuel Berg
2015-03-06 5:45 ` Cecil Westerhof
2015-03-06 9:33 ` Rusi
2015-03-10 18:34 ` Cecil Westerhof
2015-03-07 15:56 ` Emanuel Berg
2015-03-10 18:35 ` Cecil Westerhof
2015-03-11 0:35 ` Emanuel Berg [this message]
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=87pp8g1id5.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).