On Tue, Mar 16, 2004 at 01:45:26AM +0100, Denis Barbier wrote: > reassign 238189 kcontrol > thanks
Please do not play pingpong with bugs. Branden, do you have an opionion about this bug? should we split the setxkbmap stuff and kcontrol having keyboard options that do nothing? > > kcontrol uses it, so if setxkbmap has no effect either, it is clearly > > not a kcnotrol problem > If setxkbmap has no effect, kcontrol should not display those buttons, > or provide better explanations on what they do. How could kcontrol know that those options don't work, if setxkbmap doesnt tell so? The option texts are from a part of kxbd source prefixed by: // please don't change/fix messages below // they're taken from XFree86 as is and should stay the same (now there is some extra cannon fodder for the xfree86 licence change sucks) It is entirely possible, that command line kcontrol generates, setxkbmap -option caps:shift Is incorrect or wrong syntax, but without better manpage of setxkbmap, I can't really know. > I do not know what kcontrol is supposed to do, but AFAICT CapsLock can > not be emulated as on typewriters. The 'Shift cancels Caps' idiom means > that Shift+Caps prints lowercase letters (roughly); when Shift is > released, CapsLock is still locked. So if those options arent working for you, it is a problem with setxkbmap or your keyboard setup. Remember that kcontrol uses setxkbmap, and if setxkbmap fails silently, it can't really know that the specific options wont work. -- Riku Voipio | [EMAIL PROTECTED] | kirkkonummentie 33 | +358 40 8476974 --+-- 02140 Espoo | | dark> A bad analogy is like leaky screwdriver |
