From: Jason Rumney <jasonr@gnu.org>
To: Glenn Linderman <ml@g.nevcal.com>, 4836-done@emacsbugs.donarmstrong.com
Subject: bug#4836: "<S-packet> is undefined" when using AutoHotKey
Date: Sat, 14 Aug 2010 15:57:58 +0800 [thread overview]
Message-ID: <4C664C86.6090204@gnu.org> (raw)
In-Reply-To: <4AEB7897.30005@g.nevcal.com>
On 31/10/2009 7:36 AM, Glenn Linderman wrote:
> emacs 22.1.1 worked fine with autohotkey. I have macros for
> correcting my common typos, and accelerating commonly entered items,
> and entering characters not found on the keyboard.
>
> Seems none of the autohotkey macros works with emacs 23.1, instead
> they generate an error "<S-packet> is undefined".
Apparently the "packet" key code is special, so we shouldn't treat it as
a function key.
I have removed it from the list of function keys that Emacs recognizes,
so the behaviour should go back to what it was before. However my
testing shows that we cannot receive Unicode characters outside the
current codepage using VK_PACKET as Windows replaces such characters
with '?' by the time we receive them. It appears that a low level
keyboard hook may be able to retrieve the original character though, so
if we receive Lennart's cleaned up keyboard hook patches I'll try to
look at VK_PACKET support again.
next prev parent reply other threads:[~2010-08-14 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 23:36 bug#4836: "<S-packet> is undefined" when using AutoHotKey Glenn Linderman
2010-08-14 7:57 ` Jason Rumney [this message]
2010-08-25 17:06 ` bug#4836: Further information on the "<packet> undefined" error w/ keypress-modifying software? Evan Driscoll
2019-11-11 1:42 ` bug#4814: " Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2009-10-27 15:29 bug#4814: keyboard and system bug with Emacs CVS current through 2009-10-15 on w32 MON KEY
2010-02-03 1:37 ` MON KEY
2010-08-14 7:50 ` Jason Rumney
2010-08-15 23:21 ` MON KEY
2010-08-16 12:41 ` Jason Rumney
2019-10-06 5:01 ` Stefan Kangas
2019-12-15 20:20 ` Stefan Kangas
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=4C664C86.6090204@gnu.org \
--to=jasonr@gnu.org \
--cc=4836-done@emacsbugs.donarmstrong.com \
--cc=ml@g.nevcal.com \
/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).