Files
xserver_xsdl/xkb
Peter Hutterer 2fc38d1e29 xkb: add a call to init an XkbRMLVOSet from const chars
Just forcing everything to const char* is not helpful, compiler warnings are
supposed to warn about broken code. Forcing everything to const when it
clearly isn't less than ideal.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-02-04 10:53:59 +10:00
..
2014-01-12 10:24:11 -08:00
2012-03-21 13:54:42 -07:00
2012-03-21 13:54:42 -07:00
2014-01-12 10:14:49 -08:00
2012-03-21 13:54:42 -07:00
2014-01-12 10:14:49 -08:00
2003-11-14 15:54:54 +00:00
2014-01-12 10:24:11 -08:00
2012-03-21 13:54:42 -07:00
2012-03-21 13:54:42 -07:00
2012-03-21 13:54:42 -07:00
2012-07-10 00:42:09 -07:00
2012-07-10 00:42:09 -07:00
2012-03-21 13:54:42 -07:00
2012-03-21 13:54:42 -07:00
2012-12-05 18:09:48 -06:00
2012-11-05 13:25:05 -06:00
2012-03-21 13:54:42 -07:00
2012-11-05 13:25:05 -06:00
2012-11-05 13:25:05 -06:00

The X server uses this directory to store the compiled version of the
current keymap and/or any scratch keymaps used by clients.  The X server
or some other tool might destroy or replace the files in this directory,
so it is not a safe place to store compiled keymaps for long periods of
time.  The default keymap for any server is usually stored in:
     X<num>-default.xkm
where <num> is the display number of the server in question, which makes
it possible for several servers *on the same host* to share the same 
directory.

Unless the X server is modified, sharing this directory between servers on
different hosts could cause problems.