unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: w32-pass-lwindow-to-system does not work as expected
Date: Wed, 06 Jul 2005 08:54:39 +0200	[thread overview]
Message-ID: <42CB802F.8040809@student.lu.se> (raw)
In-Reply-To: <uvf3oo88b.fsf@gnu.org>

Eli Zaretskii wrote:

>I cannot do anything about your beliefs.  I wrote about the caveats
>because my experience taught me that low-level keyboard hooks bring
>maintenance headaches in the long run.
>  
>
Of course you have more experience with this.

>For example, even the simple hook you posted could conceivably raise
>some issues, if the user did some tweaking of her keyboard operation
>wrt the lwindow key (e.g., the scan code map can be modified via the
>registry).
>  
>
I never seen this possibility to enter the scan code before. From the 
documentation I read that this is new inW2k and XP. I also read that
"the mappings stored in the registry work at system level and apply to 
all users. These mappings cannot be set to work differently depending on 
the current user".

As far as understand this is not something you then can use for problems 
specific to Emacs.

And - or do I misunderstand this - more important: what you refer to are 
remapping the *scan codes* and my code used the *virtual keycodes*. That 
is what is used in Emacs today.

>On more general grounds, when Emacs users on other systems complain
>about trouble with key assignments, they are told to use system tools
>to reassign keys; we never try to solve such problems in Emacs.  Why
>do that for MS-Windows?  Shouldn't we simply advise users to use some
>key remapping tool if they want this feature so badly?
>
Perhaps, but is not that on another level? Are we not adressing issues 
within Emacs and how Emacs interacts with the system?

  reply	other threads:[~2005-07-06  6:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 19:14 w32-pass-lwindow-to-system does not work as expected Lennart Borgman
2005-07-05 19:30 ` Juanma Barranquero
2005-07-05 19:42   ` Lennart Borgman
2005-07-05 19:53     ` Juanma Barranquero
2005-07-05 20:06       ` Lennart Borgman
2005-07-05 22:17         ` Juanma Barranquero
2005-07-05 22:24           ` Lennart Borgman
2005-07-05 21:04       ` Jason Rumney
2005-07-05 22:11         ` Juanma Barranquero
2005-07-05 19:36 ` Jason Rumney
2005-07-05 19:56   ` Lennart Borgman
2005-07-05 21:08     ` Jason Rumney
2005-07-05 21:22       ` Lennart Borgman
2005-07-05 21:34 ` Eli Zaretskii
2005-07-05 20:54   ` Lennart Borgman
2005-07-06  4:43     ` Eli Zaretskii
2005-07-06  6:54       ` Lennart Borgman [this message]
2005-07-06 18:51         ` Eli Zaretskii
2005-07-06 18:23           ` Lennart Borgman
2005-07-05 22:43   ` Lennart Borgman
2005-07-06  7:08     ` Jason Rumney
  -- strict thread matches above, loose matches on Subject: below --
2005-07-06  8:36 LENNART BORGMAN

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=42CB802F.8040809@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --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).