projects / platform / upstream / libxkbcommon.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 417d074) | patch
Add a new warning for numeric keysyms
authorPierre Le Marre <dev@wismill.eu>
Mon, 18 Sep 2023 16:17:39 +0000 (18:17 +0200)
committerWismill <dev@wismill.eu>
Tue, 19 Sep 2023 06:49:52 +0000 (08:49 +0200)
commiteafd3aceca97d4984070115ec67f639b045b0d65
tree8182ee2c34ed0964eb72b1e1f786222ee2603d68tree | snapshot
parent417d0747b6dcf5cb28bd3cd6de33a0d574d7296dcommit | diff
Add a new warning for numeric keysyms

Usually it is better to use the corresponding human-friendly keysym
names. If there is none, then the keysym is most probably not
supported in the ecosystem. The only use case I see is similar to the
PUA in Unicode (see: https://en.wikipedia.org/wiki/Private_Use_Areas).
I am not aware of examples of this kind of use.
doc/message-registry.md diff | blob | history
doc/message-registry.yaml diff | blob | history
src/messages-codes.h diff | blob | history
src/xkbcomp/expr.c diff | blob | history
src/xkbcomp/parser.y diff | blob | history
tools/messages.c diff | blob | history
Domain: Graphics System / Input Management;