unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org, brakjoller@gmail.com
Subject: Re: w32-pass-lwindow-to-system (& ...rwindow)
Date: Sun, 24 Sep 2006 15:48:28 +0300	[thread overview]
Message-ID: <u8xk9l9b7.fsf@gnu.org> (raw)
In-Reply-To: <451656F5.5050105@student.lu.se> (message from Lennart Borgman on Sun, 24 Sep 2006 11:59:17 +0200)

> Date: Sun, 24 Sep 2006 11:59:17 +0200
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC:  brakjoller@gmail.com,  help-gnu-emacs@gnu.org
> 
> >> This behaviour is consistent with MS documentation. To avoid that 
> >> windows left and right keys open for example the run dialog with Win+r 
> >> you have to implement a low level keyboard hook.
> >>     
> >
> > Can you give a pointer to the Microsoft documentation which says that,
> > and/or documentation that explains how the LWIN-r combo works in terms
> > of Win32 API calls, and why it bypasses the normal keyboard reading
> > Emacs uses?
> >   
> 
> See the thread where we discussed this:
> http://lists.gnu.org/archive/html/emacs-devel/2005-07/msg00448.html

I've re-read that discussion before asking the question.  The only
pointers I found there were to a CodeProject page, which just said
that keyboard hooks were necessary, but didn't explain the issue any
further.  What I'm looking for is a more in-depth documentation,
preferably official Microsoft one.

> > I'm well aware of your patched version.  The fact is, however, that we
> > do seem to have code in w32fns.c that tries to work around the Run
> > dialog being popped.  I asked my question (above) to try to understand
> > whether that code works at all, on any Windows system.  Presumably, it
> > worked for someone at some point in the past, or else it would not
> > have been added to Emacs.
> 
> I think the documentation I pointed to in the beginning of the thread 
> answers this questions too.

Please tell where, I must have missed that somehow.

  reply	other threads:[~2006-09-24 12:48 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
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 [this message]
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=u8xk9l9b7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brakjoller@gmail.com \
    --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).