unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Switch Meta and Alt modifiers
Date: Sun, 24 Feb 2002 18:41:57 +0100	[thread overview]
Message-ID: <vafheo6g4ka.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <200202220432.g1M4WTQ13957@aztec.santafe.edu> (Richard Stallman's message of "Thu, 21 Feb 2002 21:32:29 -0700 (MST)")

Richard Stallman <rms@gnu.org> writes:

>       As Jason pointed out, a similar facility 
>     already exists in the Windows port (and another one is in the DOS port).  
>     I think it would be nice to have a single facility that is platform 
>     independent.
>
> I agree that would be an improvement.

I'm not sure but I think that this does not encompass all of the
Windows functionality.  [time passes]  Ah, for example there is the
variable w32-lwindow-modifier.  If this is nil, the key is not a
modifier but seen by Emacs as <lwindow>.  Else, the key can be seen
by Emacs as any of alt, hyper, meta, super, control, shift.

But the platform-independent mechanism (at least the one I'm thinking
of) would only transform A-x (for some modifier A and some other key
x) into H-x (for some other modifier H and the same key x).

So the closest we could get with the platform-independent mechanism
is to choose some modifier for the <lwindow> key and to have a
boolean variable which chooses whether <lwindow> is seen as that
modifier or as a normal key.

But this looses functionality.

Thoughts?

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-02-24 17:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vafzo3na09i.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
2002-02-14 10:09 ` Switch Meta and Alt modifiers Kai Großjohann
2002-02-14 12:30   ` Andreas Schwab
2002-02-15  9:38 ` Kai Großjohann
2002-02-17  5:48   ` Eli Zaretskii
2002-02-17  9:58     ` Kai Großjohann
2002-02-17 10:10       ` Eli Zaretskii
2002-02-17 15:23         ` Kai Großjohann
2002-02-17 17:00         ` Eli Zaretskii
2002-02-19  6:36           ` Richard Stallman
2002-02-19  9:31             ` Eli Zaretskii
2002-02-20 22:12               ` Richard Stallman
2002-02-21  6:44                 ` Eli Zaretskii
2002-02-22  4:32                   ` Richard Stallman
2002-02-24 17:41                     ` Kai Großjohann [this message]
2002-02-24 18:49                       ` Jason Rumney
2002-02-24 19:10                         ` Kai Großjohann
2002-02-25  0:09                       ` Richard Stallman
2002-02-25  6:03                         ` Eli Zaretskii
2002-02-21 18:59                 ` Jason Rumney
2002-02-17 11:53       ` Jason Rumney

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=vafheo6g4ka.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=eliz@is.elta.co.il \
    --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).