unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14794@debbugs.gnu.org
Subject: bug#14794: 24.3.50; `w32-register-hot-key' does not work on Windows 7 64-bit
Date: Sun, 20 Feb 2022 15:39:28 +0200	[thread overview]
Message-ID: <83v8x9wtbj.fsf@gnu.org> (raw)
In-Reply-To: <87ley5sm3n.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  20 Feb 2022 14:29:00 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Drew Adams <drew.adams@oracle.com>,  14794@debbugs.gnu.org
> Date: Sun, 20 Feb 2022 14:29:00 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Unless someone knows a way around this (I searched for it, but didn't
> > find any solutions, only complaints), I guess this will remain a
> > "known bug".
> 
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
> 
> Skimming this bug report, there doesn't seem to be anything to be done
> on the Emacs side -- or at least there wasn't eight years ago.
> 
> Is this still the case today?

I think we have a solution for this since Emacs 26.1.  From NEWS.26:

  ** Intercepting hotkeys on Windows 7 and later now works better.
  The new keyboard hooking code properly grabs system hotkeys such as
  'Win-*' and 'Alt-TAB', in a way that Emacs can get at them before the
  system.  This makes the 'w32-register-hot-key' functionality work
  again on all versions of MS-Windows starting with Windows 7.  On
  Windows NT and later you can now register any hotkey combination.  (On
  Windows 9X, the previous limitations, spelled out in the Emacs manual,
  still apply.)





  reply	other threads:[~2022-02-20 13:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<fe76a82d-41dd-4c28-8204-aa7c1e4a2aef@default>
     [not found] ` <<83fvvmuyct.fsf@gnu.org>
2013-07-10 22:28   ` bug#14794: 24.3.50; `w32-register-hot-key' does not work on Windows 7 64-bit Drew Adams
2013-07-11 16:36     ` Eli Zaretskii
2013-07-12  8:20       ` martin rudalics
2013-07-12  8:29         ` Drew Adams
2013-07-12  8:55         ` Eli Zaretskii
2022-02-20 13:29       ` Lars Ingebrigtsen
2022-02-20 13:39         ` Eli Zaretskii [this message]
2022-02-20 14:04           ` Lars Ingebrigtsen
2022-02-20 21:13           ` bug#14794: [External] : " Drew Adams
     [not found] <<c27d6591-74ce-42dc-96dd-bcb01df42b2c@default>
     [not found] ` <<83k3kw5kni.fsf@gnu.org>
2013-07-12 16:10   ` Drew Adams
2013-07-12 18:04     ` Eli Zaretskii
     [not found] <<f99844ca-a167-4256-b310-c851f1d84a42@default>
     [not found] ` <<83oba86h0q.fsf@gnu.org>
2013-07-11 21:12   ` Drew Adams
2013-07-12  6:58     ` Eli Zaretskii
     [not found] <<1bda8371-6234-45f4-a2b8-00ac282f2088@default>
     [not found] ` <<8361whuk8c.fsf@gnu.org>
2013-07-11 18:47   ` Drew Adams
2013-07-11 19:19     ` Eli Zaretskii
2013-07-04 21:10 Drew Adams
2013-07-10 17:19 ` Eli Zaretskii

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=83v8x9wtbj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14794@debbugs.gnu.org \
    --cc=larsi@gnus.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).