Ran Benita 4b69d6f71d keycodes: ignore explicit minimum/maximum statements ... These statements are pretty pointless for us; we don't restrict keycodes like X does, and if someone writes e.g. maximum = 255 but only has 100 keys, we currently happily alloc all those empty keys. xkbcomp already handles the case when these statements aren't given, and uses a computed min/max instead. We should just always use that. (Of course since keycodes/evdev currently uses almost all of the keycodes in the range it declares, including 255, this doesn't save any memory for the common user right now). Signed-off-by: Ran Benita <ran234@gmail.com>		2012-09-15 02:09:34 +03:00
..
bad.xkb	Move test data files to test/data/keymaps	2012-07-12 14:14:50 +01:00
basic.xkb	Import dataset into test/data/	2012-07-12 14:48:49 +01:00
comprehensive-plus-geom.xkb	Move test data files to test/data/keymaps	2012-07-12 14:14:50 +01:00
default.xkb	Import dataset into test/data/	2012-07-12 14:48:49 +01:00
divide-by-zero.xkb	expr: don't divide by zero	2012-07-26 23:15:54 +03:00
no-types.xkb	types: don't use canonical/required types	2012-08-07 13:20:37 +03:00
stringcomp.data	keycodes: ignore explicit minimum/maximum statements	2012-09-15 02:09:34 +03:00