[Xquartz-dev] 2.5.0_beta2

[Jean-Francois Sygnet]

Hi

You may be aware of the info below, or not:

On my macbookpro1,1 running 10.6.2 and 2.5.0_beta2,
(and no ~/.* files :-) there seem to be a problem
involving CAPS-LOCK and the top (US) keyboard row:

In any xterm or xedit or emacs or xev ...

Top Row (xev state 0x0):
`1234567890-=

Top Row + SHIFT (xev state 0x1):
~!@#$%^&*()_+

Top Row + CAPS-LOCK (xev state 0x2):
~!@#$%^78(0-+

Top Row + CAPS-LOCK + SHIFT (xev state 0x3):
`1233456&*9)_=

looks like only keys 7, 8, 0, and -
behave properly.

Am I the only one with this odd behavior ?

JF Sygnet

Jeremy Huddleston wrote:
> The XKB issue is 50% fixed.  I'm glad that your use case is working, 
> but other users should not panic if they're still having some problems.  
> I believe the remaining issue should be restricted to some keys 
> repeating that shouldn't and others that don't repeat that should.  
> This is because the "should we repeat" metadata is being inherited 
> from an incorrect keymap and not getting clobbered correctly anymore.
> 
> I have what I think can be a workaround for the remaining issues, 
> but I'm not satisfied with it 100% yet.  It should be there in rc1 
> (which I hope to have ready in a few weeks).
> 
> Thanks for the feedback,
> Jeremy
> 
> On Feb 6, 2010, at 00:44, Marcus Crestani wrote:
> 
>> "JH" == Jeremy Huddleston <jeremyhu at apple.com> writes:
>> JH> I've once again rolled a new beta release of XQuartz.  2.5.0_beta2
>> JH> includes multiple bug fixes for issues recently marked as "fixed" in
>> JH> trac.  Please check out the full ChangeLog for details.
>>
>> Works fine for me, especially XKB's problem with keyboard shortcuts
>> seems to be fixed.
>>
>> Thanks!
>>
>> -- 
>> Marcus