From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: w32-enable-(caps|num)-lock vs typematic keyboard
Date: Thu, 30 Nov 2006 12:34:20 +0100 [thread overview]
Message-ID: <f7ccd24b0611300334h6f3f51dfp328102ba6aa630de@mail.gmail.com> (raw)
In-Reply-To: <u4pshbmp6.fsf@gnu.org>
On 11/30/06, Eli Zaretskii <eliz@gnu.org> wrote:
> And then what? You said:
>
> if you keep the key down on a typematic keyboard the caps-lock or
> num-lock state can still change
>
> Does that mean that I press and hold the `d' key, for instance, and
> after some time the CapsLock key goes on?
No. In my message "the key" tried to mean "they key affected by the
variable previously referred to".
In other words:
ELISP> (setq w32-enable-caps-lock nil)
nil
And now I press Caps Lock and keep it down: the caps lock light
flickers like mad. I release the key: the light flicks a few moments
more (while the typematic buffer lasts, I suppose), and then stops.
Sometimes on, sometimes off.
The same thing happens with `w32-enable-num-lock' and the Num Lock key.
/L/e/k/t/u
next prev parent reply other threads:[~2006-11-30 11:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 17:17 w32-enable-(caps|num)-lock vs typematic keyboard Juanma Barranquero
2006-11-29 19:04 ` Eli Zaretskii
2006-11-29 19:30 ` Juanma Barranquero
2006-11-29 19:59 ` Lennart Borgman
2006-11-29 20:03 ` Juanma Barranquero
2006-11-30 4:08 ` Eli Zaretskii
2006-11-30 11:34 ` Juanma Barranquero [this message]
2006-11-30 12:53 ` Lennart Borgman
2006-11-30 13:26 ` Juanma Barranquero
2006-11-30 15:49 ` Lennart Borgman
2006-11-30 16:10 ` Juanma Barranquero
2006-11-30 16:17 ` Lennart Borgman
2006-11-30 16:32 ` Juanma Barranquero
2006-11-30 20:09 ` Eli Zaretskii
2006-11-30 20:19 ` Juanma Barranquero
2006-11-30 20:43 ` Eli Zaretskii
2006-11-30 21:41 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0611300334h6f3f51dfp328102ba6aa630de@mail.gmail.com \
--to=lekktu@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.