GNU bug report logs - #4814
keyboard and system bug with Emacs CVS current through 2009-10-15 on w32

Previous Next

Full log

Message #22 received at 4814 <at> debbugs.gnu.org (full text, mbox):

From: Evan Driscoll <driscoll <at> cs.wisc.edu>
To: 4814 <at> debbugs.gnu.org, 4836 <at> debbugs.gnu.org
Subject: Further information on the "<packet> undefined" error w/
	keypress-modifying software?
Date: Wed, 25 Aug 2010 12:06:41 -0500

[Message part 1 (text/plain, inline)]

I just ran across a small annoyance today, and in looking for a solution
ran across these two bugs. 4836 sounds like it's very closely related to
what I'm seeing, and there's some discussion about how it relates to
4814, so here goes.


Brief description:
  Using Emacs >=23 with AllChars causes an error message "<packet>
  is undefined" to appear when entering a compose key sequence.


How I did caused the bug to surface:

 - Install AllChars (http://sourceforge.net/projects/allchars/).
   This is a program that gives Windows a compose key feature.
 - Install Emacs >=23.
 - Start AllChars with the default configuration, start Emacs.
 - Try to use a compose-key sequence, e.g. '<compose> / o' or
   '<compose> ` a'. (By default, <compose> is <menu>, but I tried
   another option or two.)


Symptoms:

 - In Emacs 22.3, the composed character (ø or à) shows up as
   expected
 - In Emacs 23.1 and 23.2, as well as CVS Emacs distributed at
   ntemacs.sourceforge.net, an error in the minibuffer is
   displayed: "<packet> is undefined"

Hopefully this'll help.

Evan Driscoll

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.