From: Cecil Westerhof <Cecil@decebal.nl>
To: help-gnu-emacs@gnu.org
Subject: Re: <Multi_key> does not work anymore
Date: Tue, 10 Mar 2015 19:34:01 +0100 [thread overview]
Message-ID: <87r3sw3dnq.fsf@Equus.decebal.nl> (raw)
In-Reply-To: 03b6df78-35f2-4689-a443-84879a50ece9@googlegroups.com
Op Friday 6 Mar 2015 10:33 CET schreef Rusi:
> On Friday, March 6, 2015 at 11:36:03 AM UTC+5:30, Cecil Westerhof wrote:
>> Op Friday 6 Mar 2015 01:02 CET schreef Emanuel Berg:
>>
>>> Cecil Westerhof writes:
>>>
>>>>> In my .xmodmap I have: keycode 135 = Multi_key With
>>>>> this I could always use the menu-key followed by
>>>>> two spaces to get a non-break space. In other
>>>>> programs it still works like this, but in Emacs I
>>>>> get now: <Multi_key> is undefined What is happening
>>>>> here?
>>>>
>>>> The interesting bid is that in Emacs with root it
>>>> still works.
>>>
>>> Did you modify the keymap for the root user as well?
>>>
>>> If Emacs says "<Multi_key> is undefined" then it
>>> should be easy enough to solve this, just define
>>> (bind) it to do whatever you want. If you want it to
>>> be a key sequence probably you need to make it a
>>> "prefix key" as well, as in:
>>>
>>> ; step 1 - name
>>> (define-prefix-command 'C-o-prefix)
>>>
>>> ; step 2 - bind
>>> (global-set-key "\C-o" 'C-o-prefix)
>>>
>>> ; step 3 - normal usage as you would any key
>>> (global-set-key "\C-\M-j" 'scroll-left-1)
>>> ; ...
>>
>> It has nothing to do with Emacs: it is done with xmodmap, so it is
>> an X binding not an Emacs binding. This is something I defined
>> years ago (globally, so for normal user and root user) and always
>> worked. I did not change anything in .xnodmap or in .emacs. So this
>> should not be happening, but it is.
>
>
> Specific:
>
> May be related to this issue See thread
> https://groups.google.com/d/msg/gnu.emacs.help/hBA42H2chGM/2Xfa1ce2LlMJ
That solved the problem (I think, because in the thread is said it
works sometimes). But two things:
- It started happening when I upgrade my Linux version.
- For root (where I do not have this problem) XMODIFIERS is not
defined.
So I now use:
/usr/bin/env -u XMODIFIERS /usr/bin/emacs
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
next prev parent reply other threads:[~2015-03-10 18:34 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 [this message]
2015-03-07 15:56 ` Emanuel Berg
2015-03-10 18:35 ` Cecil Westerhof
2015-03-11 0:35 ` Emanuel Berg
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=87r3sw3dnq.fsf@Equus.decebal.nl \
--to=cecil@decebal.nl \
--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).