On Wednesday, May 3 2006 01:29, Denis Barbier wrote:
> On Thu, Apr 27, 2006 at 06:05:03PM +0300, Shai Berger wrote:
> > Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc.
>
> Setting XKBPATH works fine for me, can you please explain how you proceed
> so that I can reproduce your problem?
>
I set XKBPATH up in my .profile, log in on vt1, and type this command:
$ XKBPATH=$XKBPATH XPSERVERLIST=:64 LANG=en_US.UTF-8 startx -- :1 -dpi 96
(yes, I know the beginning is superfluous, but I typed it like that once, and
now I only use history to bring it up). When the session is started, if I
check it in an xterm, the environment variable is set, but I do not see the
effects (the difference is that with my setup, alt-caps changes keyboard
layouts).
I use KDE, and when I tried to do what I said I'd do (run a "setxkbmap |
xkbcomp" in .xinitrc) it didn't work -- I had to do it in KDE's autostart,
that is, after the WM is up. I suspected KDE was doing something funny, so I
tried IceWM -- there, too, the XKBPATH was not respected, although it was
defined in shells in xterms (IceWM was started from an .xinitrc file).
However, with IceWM, running the setxkbmap|xkbcomp pipe in .xinitrc did work.
Hope this helps, and thanks for your efforts,
Shai.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
