On Wed, 06 Aug 2003 12:43:26 +0200, Frank Murphy wrote:
>> Funny, this one caused the Apple/Command key to produce M-s,
>> that is, Meta-Super.
>
> That is so whack. I'm not getting any of the same results you do.
Do you have a second server as well?
> I had another idea. It seems that altwin:meta_win gives you what you want,
> but
> only on display :0.
Yes!
> Run the program `setxkbmap -v 6`; it should show you the list of Xkb mappings
> it applies by default (and applies them). I bet the results are different on
> :0 and :1. Or by running this on :1, it will set the altwin:meta_win to what
Yes!
In :0, I get:
~ $ setxkbmap -v 6
Trying to build keymap using the following components:
keycodes: xfree86
types: complete
compat: complete
symbols: us(pc101)+us_intl+altwin(meta_win)
geometry: pc(pc101)
~ $
But in :1, I get:
/var/tmp $ setxkbmap -v 6
Trying to build keymap using the following components:
keycodes: xfree86
types: complete
compat: complete
symbols: macintosh/us(extended)+macintosh/us_intl(ibook)+altwin(meta_win)
geometry: macintosh(macintosh)
Error loading new keyboard description
/var/tmp $
So once again it seems to me that :1 is trying to use the
console conf... don't ask me how.
> you want. If it shows differences, you can use setxkbmap -option
> altwin:meta_win (or something) to set them to the same thing.
/var/tmp $ setxkbmap -geometry "pc(101)" -symbols
"us(pc101)+us_intl+altwin(meta_win)"
Error loading new keyboard description
/var/tmp $
Is there a secret here? I also tried loading the symbols as
discreet options, to no avail...
> If that works, then there's a bug with how XFree handles alternate kemaps on
> secondary displays.
I guess so. Should I then report it, or perhaps wait to test 4.3?
>> Yes, GNU/Linux is still far away from the average user...
>
> Yeah. Anything having to do with low-level access for common desktop needs is
> underpowered. Keyboard, mouse, sound, USB. It's coming together, but slowly.
> I think the real requirements aren't well defined, so there are a lot of
> different solutions. Just look at the list of sound solutions!
One thing that baffles me is that X and console have redundant
confs. Shouldn't there be a way of telling X to just use the console
input drivers, and ideally also the framebuffer ones? But I guess X
have much more developed drivers, so perhaps the console should use
the X ones, but then ugh...
--
_ Leandro Guimarães Faria Corsetti Dutra +41 (21) 648 11 34
/ \ http://br.geocities.com./lgcdutra/ +41 (78) 778 11 34
\ / Answer to the list, not to me directly! +55 (11) 5686 2219
/ \ Rate this if helpful: http://svcs.affero.net/rm.php?r=leandro
