Portál AbcLinuxu, 8. května 2024 05:22
If you have an Xserver and a client shell running on different comput-
ers and XKB configuration files sets on those machines are different
you can get problems specifying a keyboard map by model, layout,
options names. The thing is the setxkbcomp converts these names to
names of XKB configuration files according to files that are on the
client side computer. Then it sends the file names to the server where
the xkbcomp has to compose a complete keyboard map using files which
the server has. Thus if the sets of files differ significantly the
names that the setxkbmap generates can be unacceptable on the server
side. You can solve this problem running the xkbcomp on the client
side too. With the -print option setxkbmap just prints the files names
in an appropriate format to its stdout and this output can be piped
directly to the xkbcomp input. For example, a command
setxkbmap us -print | xkbcomp - $DISPLAY
makes both step on the same (client) machine and loads a keyboard map
into the server.
Doufam, ze je z to z toho jasny.
xmodmap -e 'keycode 52 = y' xmodmap -e 'keycode 29 = z'Nastaví to qwertz. A raději už nikdy neříkej "tenký klient". Z pohledu X se jedná o server.
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.