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
..
compat	Import dataset into test/data/	2012-07-12 14:48:49 +01:00
keycodes	rulescomp: remove bad failtests	2012-09-01 10:58:10 +03:00
keymaps	keycodes: ignore explicit minimum/maximum statements	2012-09-15 02:09:34 +03:00
rules	rules: fix check for appending '|' character when applying	2012-09-03 10:31:12 +03:00
symbols	test/data/symbols: keypad can only have one default section	2012-09-03 10:31:12 +03:00
types	Import dataset into test/data/	2012-07-12 14:48:49 +01:00