mirror of
https://github.com/X11Libre/xserver.git
synced 2026-03-24 05:54:08 +00:00
742443ea73
The keymap assembly machinery is a horribly complicated machinery, because often whole replies with variable sized payloads can be nested into each other. It's time to use x_rpcbuf_t for that, but's is not an easy thing to do and really a huge change - therefore doing this in small and easy to digest step. At first, let XkbAssembleMap() operate on a x_rpcbuf_t. But for now just let it use the x_rpcbuf_t's raw buffer directly (because it's callees cant work on this yet) - thus XkbAssembleMap() yet need to make enough room in the buffer before calling in. For the time being we're allocating far too much (because calculating the actually need amount would be too complicated here) and having an extra memcpy(). But it's just an intermediate step anyways - subsequent commits will convert everything down the whole call chain into using x_rpcbuf_t operations, so that extra overhead can be dropped again later. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
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.