From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Aleix Conchillo Flaqué" <aleix@member.fsf.org>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: ctrl:nocaps enables mark set?
Date: Wed, 03 Sep 2008 23:03:35 +0900 [thread overview]
Message-ID: <878wu9498o.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <b890d37d0809030555o4e8fd5fbj661d5908f725ecaf@mail.gmail.com>
Aleix Conchillo Flaqué writes:
> On Tue, Sep 2, 2008 at 20:54, Andreas Schwab <schwab@suse.de> wrote:
> > "Aleix Conchillo Flaqué" <aleix@member.fsf.org> writes:
> >
> >> KeyRelease event, serial 33, synthetic NO, window 0x3600001,
> >> root 0x8b, subw 0x0, time 82422761, (109,-9), root:(113,36),
> >> state 0x6, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
> > ^^^
> >
> > This is bad. You have keycode 66 on both the control and lock modifier
> > list.
> >
>
> I have reviewed my email and capslock has keycode 66 and ctrl has
> keycode 37 both producing Control_L.
True.
The problem is that there is also a feature of the X server that it
maintains up/down state for certain keys because it is so common to
check for chords with those keys. Specifically, the modifier keys.
As Andreas points out, your keycode 66 is in the list of modifiers as
BOTH a shiftlock key and a control key. You need to fix the modifier
list, not the keysym definition, of the key corresponding to 66.
In-hopes-of-avoiding-flame-from-Andreas-who-really-knows-his-stuff-ly y'rs
next prev parent reply other threads:[~2008-09-03 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 15:23 ctrl:nocaps enables mark set? Aleix Conchillo Flaqué
2008-09-02 16:13 ` Andreas Schwab
2008-09-02 16:19 ` Aleix Conchillo Flaqué
2008-09-02 18:54 ` Andreas Schwab
2008-09-02 19:47 ` Aleix Conchillo Flaqué
2008-09-03 12:55 ` Aleix Conchillo Flaqué
2008-09-03 14:03 ` Stephen J. Turnbull [this message]
2008-09-03 14:09 ` Aleix Conchillo Flaqué
2008-09-02 16:18 ` Chong Yidong
2008-09-02 16:22 ` Aleix Conchillo Flaqué
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=878wu9498o.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=aleix@member.fsf.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.