From: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: w32-pass-lwindow-to-system (& ...rwindow)
Date: Sun, 24 Sep 2006 15:59:10 +0300 [thread overview]
Message-ID: <u64fdl8td.fsf@gnu.org> (raw)
In-Reply-To: <f0204$4515792d$49f2031$30579@DIALUPUSA.NET> (ecinmn@alcisp.com)
> From: "B. T. Raven" <ecinmn@alcisp.com>
> Date: Sat, 23 Sep 2006 13:17:57 -0500
>
> "Mathias Dahl" <brakjoller@gmail.com> wrote in message
> news:upsdmikql.fsf@gmail.com...
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > Looks like the trick we play around line 3005 of w32fns.c isn't
> > > working. What Windows version is that? Is there someone on this
> > > list who can make LWIN-r combo work for them in Emacs, in any
> > > version of Windows?
> >
> > I just tested with emacs -q and it works as for the parent poster,
> > i.e. Win+s gives me `search-backward-regexp' but Win+r opens up the
> > Run dialog. The same applies for Win+e (open Explorer.exe).
> >
> > I use CVS Emacs from 2006-03-20 on Windows XP.
> >
> > /Mathias
>
> I have w98 and w2000 but I have tried it only on w98 (ver 21.3) so far.
> In addition to win-e, win-f, win-d,and win-r, win-m is also a problem
> (apparently it is a synonym for win-d, raise the desktop.) The other
> unassigned s-<whatever> keychords produce a pleasant ding sound. I will
> test it on w-2000 when I get a chance but there I have only version 22.0
> installed.
>
> Probably not relevant, but the following work alright:
>
> (global-set-key [(super g)] 'goto-line)
> (global-set-key [(super b)] 'bury-buffer)
> (global-set-key [(super k)] (lambda () (interactive) (kill-line 0 )))
Thanks to all who responded.
I now think that my original opinion about the code in w32fns.c no
working was in error. That code _does_ work, and correctly prevents
Windows from popping up the Start menu when lwindow is pressed and
released without pressing any other key. This is important when
w32-pass-lwindow-to-system is set to nil, but w32-lwindow-modifier is
left at its default nil value, which causes the lwindow key to appear
in Emacs as <lwindow>.
But the case of <lwindow>-r, when w32-lwindow-modifier is set to
`super', cannot be handled by that trick, because Windows seems to
catch the combo before Emacs gets the chance to process it.
Sorry for any confusion I might have caused.
next prev parent reply other threads:[~2006-09-24 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 0:46 w32-pass-lwindow-to-system (& ...rwindow) B. T. Raven
2006-09-23 15:44 ` Eli Zaretskii
[not found] ` <mailman.7285.1159026303.9609.help-gnu-emacs@gnu.org>
2006-09-23 16:57 ` Mathias Dahl
2006-09-23 18:17 ` B. T. Raven
2006-09-24 12:59 ` Eli Zaretskii [this message]
2006-09-24 16:45 ` Eli Zaretskii
[not found] ` <mailman.7319.1159116339.9609.help-gnu-emacs@gnu.org>
2006-09-25 0:32 ` B. T. Raven
2006-09-25 3:21 ` Eli Zaretskii
[not found] ` <mailman.7336.1159154474.9609.help-gnu-emacs@gnu.org>
2006-09-25 11:55 ` B. T. Raven
2006-09-24 0:50 ` Lennart Borgman
2006-09-24 7:13 ` Eli Zaretskii
2006-09-24 9:59 ` Lennart Borgman
2006-09-24 12:48 ` Eli Zaretskii
2006-09-24 13:19 ` Lennart Borgman
[not found] ` <mailman.7293.1159059034.9609.help-gnu-emacs@gnu.org>
2006-09-24 3:34 ` B. T. Raven
2006-09-24 7:08 ` Eli Zaretskii
2006-09-24 10:19 ` 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=u64fdl8td.fsf@gnu.org \
--to=eliz@gnu.org \
--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).