ctrl:nocaps enables mark set?

ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

Hi,

with the latest emacs cvs versions (over the last two weeks) when I
use C-n or C-p (C=Caps lock) the "Mark is set". It does not happen
when I press the normal Ctrl key.

I have tried it with "emacs -q". My box is Debian GNU/Linux testing. I
am using GNOME, but the same happens with Openbox.

Emacs CVS from 2008-08-29 (23.0.60.1).

Configure command:

./configure --prefix=/home/aleix/bin/emacs/2008-08-29
--with-x-toolkit=gtk --with-xft --with-xpm --with-jpeg --with-tiff
--with-png --with-rsvg

Is there anything I can do to provide you more information? Or some
test I could perform?

Thanks in advance,

Aleix

Re: ctrl:nocaps enables mark set?

[Andreas Schwab]

"Aleix Conchillo Flaqué" <aleix@member.fsf.org> writes:

> Is there anything I can do to provide you more information? Or some
> test I could perform?

What does xev say when you press/release the CapsLock-as-Ctrl key?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

On Tue, Sep 2, 2008 at 6:13 PM, Andreas Schwab <schwab@suse.de> wrote:
> "Aleix Conchillo Flaqué" <aleix@member.fsf.org> writes:
>
>> Is there anything I can do to provide you more information? Or some
>> test I could perform?
>
> What does xev say when you press/release the CapsLock-as-Ctrl key?
>

For the CapsLock:

KeyPress event, serial 33, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 82422639, (109,-9), root:(113,36),
    state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
    XKeysymToKeycode returns keycode: 37
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

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,
    XKeysymToKeycode returns keycode: 37
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

For the normal Ctrl key:

KeyPress event, serial 33, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 82373457, (72,-12), root:(76,33),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 82373612, (72,-12), root:(76,33),
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Re: ctrl:nocaps enables mark set?

[Andreas Schwab]

"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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

On Tue, Sep 2, 2008 at 20:54, Andreas Schwab <schwab@suse.de> wrote:
>
>> 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.
>

Any idea what can cause that? Or where can I ask?

Aleix

Re: ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

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.

Maybe you confused the press and release parts...

Aleix

Re: ctrl:nocaps enables mark set?

[Stephen J. Turnbull]

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

Re: ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

On Wed, Sep 3, 2008 at 16:03, Stephen J. Turnbull <stephen@xemacs.org> wrote:
>  >
>  > 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
>

OK, got it now. Sorry, I get a bit lost when talking about modifiers,
keycodes, keysyms... :-(

Aleix

Re: ctrl:nocaps enables mark set?

[Chong Yidong]

"Aleix Conchillo Flaqué" <aleix@member.fsf.org> writes:

> with the latest emacs cvs versions (over the last two weeks) when I
> use C-n or C-p (C=Caps lock) the "Mark is set". It does not happen
> when I press the normal Ctrl key.
>
> I have tried it with "emacs -q". My box is Debian GNU/Linux testing. I
> am using GNOME, but the same happens with Openbox.

Check xev; this may be a misconfigured Xmodmap.  Does your caps lock key
issue a shift modifier, in addition to a control modifier?

Re: ctrl:nocaps enables mark set?

[Aleix Conchillo Flaqué]

On Tue, Sep 2, 2008 at 6:18 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
>
> Check xev; this may be a misconfigured Xmodmap.  Does your caps lock key
> issue a shift modifier, in addition to a control modifier?
>

As far as I know, no.

With Openbox I did not load any Xmodmap file. And the only one I
normally use is:

$ cat .xmodmap
clear mod1
clear mod4
keycode 0x73 = Alt_L
keycode 0x40 = Meta_L
add mod4 = Alt_L
add mod1 = Meta_L