You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contrary to keymap files, the ! include statement in rules does not lookup include paths added to xkb_context. So it is not possible e.g. to import another file in the same folder without using an absolute path.
I know the first intended use is using system path, e.g. ! include %S/evdev (see #108), but I expected to be able to use the statement as the keymap one.
My current use case is to be able to modify the rules for the tests in #450 without duplicating the whole rule file. I want to be able to use ! include evdev and resulting in including the first file named rules/evdev found in the xkb_context include paths. Meanwhile I defined XKB_CONFIG_ROOT and used %S.
Apart from that, this is for consistency with the rest of the lib. So low priority.
PS: I did not realize that ! include is not supported by XOrg tools. Might be worth added a note in the compatibility page and in the rule file page.
The text was updated successfully, but these errors were encountered:
Contrary to keymap files, the
! include
statement in rules does not lookup include paths added toxkb_context
. So it is not possible e.g. to import another file in the same folder without using an absolute path.I know the first intended use is using system path, e.g.
! include %S/evdev
(see #108), but I expected to be able to use the statement as the keymap one.My current use case is to be able to modify the rules for the tests in #450 without duplicating the whole rule file. I want to be able to use
! include evdev
and resulting in including the first file namedrules/evdev
found in thexkb_context
include paths. Meanwhile I definedXKB_CONFIG_ROOT
and used%S
.Apart from that, this is for consistency with the rest of the lib. So low priority.
PS: I did not realize that
! include
is not supported by XOrg tools. Might be worth added a note in the compatibility page and in the rule file page.The text was updated successfully, but these errors were encountered: