On 2022-04-23 23:57:24 +0200, Vincent Lefevre wrote:
[...]
> where .xkb/keymap/test contains
>
> xkb_keymap {
> xkb_keycodes { include "evdev+aliases(qwerty)" };
> xkb_types { include "complete" };
> xkb_compat { include "complete" };
> xkb_symbols { include "pc+gb+inet(evdev)" };
> xkb_geometry { include "pc(pc105)" };
> };
>
> Either these are real bugs or these are just spurious warnings that
> should be licenced by default.
^^^^^^^^ I meant "silenced"
It could also be that xkb-data has obsolete or invalid keys.
> Some of them are common with bug 756268.
(which was in 2014).
> Most of them can be silenced with "-w 0", but the user shouldn't need
> to provide "-w 0" since it is not his fault.
FYI, except for the XF86EmojiPicker one (bug 1009995), a first warning
starts with -w 2:
zira:~> xkbcomp -w 2 -I$HOME/.xkb -R$HOME/.xkb keymap/test xkb.dump
Keycodes above 256 (e.g. <I256>) are not supported by X and are ignored
Warning: Could not resolve keysym XF86EmojiPicker
> For warnings not silenced by "-w 0", this is bug 1009994.
Currently, this concerns the XF86EmojiPicker one only.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
