unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Subject: Re: Xfree86 and the Meta key (+patch)
Date: Mon, 4 Oct 2004 02:08:17 +0200 (CEST)	[thread overview]
Message-ID: <20041004000840.PMNH3239.mxfep01.bredband.com@coolsville.localdomain> (raw)

> "Jan D." <jan.h.d@swipnet.se> writes:
> 
> > I think there is something "wrong" in Xorg also.  It behaves exactly as
> > described in the bug report.  Andreas, do you have an unmodified Xorg,
> > with standard xkb maps and no xmodmap settings, and still manage to get
> > Meta on the "Windows"-key using altwin:meta_win (i.e. assigning Meta to
> > the "Windows"-key) as an option to xkb?
> 
> What does altwin:meta_win do exactly in terms of modifier keys?  Actually
> I'm using a modified keymap with some modifier keys remapped: <LMTA> and
> <RMTA> are emitting Alt_L and Alt_R, resp., and <LALT> is changed to emit
> Meta_L (the unmodified map has them the other way round).

altwin:meta_win assignes Meta_L/R to the "Window"-keys (<LWIN> and <RWIN>,
default is Super_L/Multi_Key) and Meta_L/R is added to Mod4 (Mod1 is Alt_L/R).

Previously Mod4 was Super_L on <LWIN>, and when altwin:meta_win was set
Mod4 became Meta_L/R.

Now Mod4 is Super_L and Hyper_L on "fake" keys.  altwin:meta_win then
just adds Meta_L/R, so Emacs sees Mod4 as Hyper-Super-Meta.

If there is no need for these fake keys (I am not sure what they do),
you could set altwin:meta_win and then do

% xmodmap -e 'remove mod4 = Hyper_L' -e 'remove mod4 = Super_L'

and get the same behaviour as previous X versions.

I'm not sure why your modification works with Xorg, probably your Meta_L/R
are on a different modifier (Mod3 for example).  Or maybe your keymap
does not have them.

	Jan D.

             reply	other threads:[~2004-10-04  0:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04  0:08 Jan D. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-04 21:30 Xfree86 and the Meta key (+patch) Denis Barbier
2004-10-04 22:56 ` Jan D.
2004-10-05  5:53   ` Denis Barbier
2004-10-05 10:43     ` Jan D.
2004-10-05 19:50       ` Denis Barbier
     [not found] <20041003233940.JVGC27821.mxfep02.bredband.com@coolsville.localdomain>
2004-10-03 23:52 ` Andreas Schwab
2004-10-01 21:00 Jérôme Marant
2004-10-02 23:06 ` Kim F. Storm
2004-10-03  7:34   ` Jérôme Marant
2004-10-04 15:18     ` Richard Stallman
2004-10-04 15:55       ` Jérôme Marant
2004-10-05 18:05         ` Richard Stallman
2004-10-05 21:07           ` Jérôme Marant
2004-10-05 21:15             ` Jan D.
2004-10-03  8:11   ` Frank Schmitt
2004-10-03 12:00     ` Jan D.
2004-10-03 17:54       ` Andreas Schwab
2004-10-03 19:10         ` Jérôme Marant
2004-10-03 21:07           ` Andreas Schwab
2004-10-03 21:52           ` Jan D.
2004-10-03 22:48             ` Andreas Schwab

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=20041004000840.PMNH3239.mxfep01.bredband.com@coolsville.localdomain \
    --to=jan.h.d@swipnet.se \
    /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).