From: Klaus Zeitler <kzeitler@lucent.com>
Cc: emacs-devel@gnu.org
Subject: Re: Num_Lock under solaris 5.8
Date: Fri, 12 May 2006 14:30:14 +0200 [thread overview]
Message-ID: <q5g1wuzjui1.fsf@sfsw51.de.lucent.com> (raw)
In-Reply-To: <44647B79.8060709@swipnet.se> (Jan Djärv's message of "Fri, 12 May 2006 14:11:37 +0200")
>>>>> "Jan" == Jan Djärv <jan.h.d@swipnet.se> writes:
Jan>
Jan> And xev says...?
Pressing Num_lock, then KP_7, then Num_lock and KP_7 again I get:
KeyRelease event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680513068, (31,48), root:(48,594),
state 0x20, keycode 90 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 characters: ""
KeyPress event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680514916, (31,48), root:(48,594),
state 0x0, keycode 90 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 characters: ""
KeyPress event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680523252, (31,48), root:(48,594),
state 0x20, keycode 102 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 characters: ""
KeyRelease event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680523428, (31,48), root:(48,594),
state 0x20, keycode 102 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 characters: ""
KeyRelease event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680525507, (31,48), root:(48,594),
state 0x20, keycode 90 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 characters: ""
KeyPress event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680526923, (31,48), root:(48,594),
state 0x0, keycode 102 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 characters: ""
KeyRelease event, serial 29, synthetic NO, window 0x9800001,
root 0x25, subw 0x9800002, time 680527043, (31,48), root:(48,594),
state 0x0, keycode 102 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 characters: ""
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
Come to think of it, there are already a million monkeys on a million
typewriters, and Usenet is NOTHING like Shakespeare. -- Blair Houghton
next prev parent reply other threads:[~2006-05-12 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 10:01 Num_Lock under solaris 5.8 Klaus Zeitler
2006-05-12 10:18 ` Jan Djärv
2006-05-12 11:02 ` Klaus Zeitler
2006-05-12 11:39 ` Jan Djärv
2006-05-12 11:40 ` Jan Djärv
2006-05-12 11:47 ` Klaus Zeitler
2006-05-12 12:11 ` Jan Djärv
2006-05-12 12:30 ` Klaus Zeitler [this message]
2006-05-12 12:57 ` Jan Djärv
2006-05-12 13:20 ` Klaus Zeitler
2006-05-12 13:57 ` Jan Djärv
2006-05-15 9:10 ` Klaus Zeitler
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=q5g1wuzjui1.fsf@sfsw51.de.lucent.com \
--to=kzeitler@lucent.com \
--cc=emacs-devel@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.
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).