xkbcomp: Changes to 'master'
Daniel Stone
daniels at kemper.freedesktop.org
Tue Jun 21 06:13:46 PDT 2011
compat.c | 9 ++++++++-
configure.ac | 2 +-
2 files changed, 9 insertions(+), 2 deletions(-)
New commits:
commit e68a8ef1067f98056237d8067052e2a0d9896133
Author: Daniel Stone <daniel at fooishbar.org>
Date: Tue Jun 21 14:06:05 2011 +0100
Bump to 1.2.2
Emergency bugfix for the syminterp declarations. They've been broken
since the beginning of time, but I guess we just haven't added new
interpreted symbols since around then.
Signed-off-by: Daniel Stone <daniel at fooishbar.org>
commit 2a473b906943ffd807ad81960c47530ee7ae9a60
Author: Daniel Stone <daniel at fooishbar.org>
Date: Tue Jun 21 14:03:53 2011 +0100
Interp: Ignore NoSymbol definitions
A NoSymbol syminterp leads to a Any+AnyOfOrAll(None) definition, which
is never what anyone would actually ever want in a sym interp. The
failure mode here was:
interpret XF86SomeKeysymYouDontHaveYet {
action=Something()
}
leading to:
interpret Any+AnyOfOrAll(None) {
action=Something()
}
leading to every single non-action key triggering your shiny new action
that was only supposed to come from a new keysym.
At least you could VT switch or zap, I guess.
Later, more invasive, revisions will bring a more useful error message.
Signed-off-by: Daniel Stone <daniel at fooishbar.org>
commit a2816345e58c88f5806a5c6df310c7d9c62264f0
Author: Daniel Stone <daniel at fooishbar.org>
Date: Tue Jun 21 14:03:12 2011 +0100
Interp: Don't make modifier lookup failure fatal
If we can't look up a modifier in a SymInterp declaration, don't make
that fatal enough to kill the entire file, just ignore it and move on.
Signed-off-by: Daniel Stone <daniel at fooishbar.org>
More information about the xorg-commit
mailing list