1. 25 Jan, 2017 3 commits
  2. 24 Jan, 2017 1 commit
  3. 19 Jan, 2017 2 commits
  4. 16 Jan, 2017 4 commits
  5. 12 Jan, 2017 7 commits
  6. 11 Jan, 2017 4 commits
  7. 10 Jan, 2017 1 commit
  8. 04 Jan, 2017 1 commit
    • Mihail Konev's avatar
      xkb: Match key releases with an overlaid press · 9d32b71c
      Mihail Konev authored
      
      
      Testcase:
      
      In ~/.xbindkeysrc:
        "xterm &"
             XF86LaunchA
      
      In ~/ov.xkb:
        xkb_keymap {
            xkb_keycodes { include "evdev" };
            xkb_types    { include "complete" };
            xkb_compat   { include "complete"
                interpret Overlay1_Enable+AnyOfOrNone(all) {
                    action= SetControls(controls=Overlay1);
                };
            };
            xkb_symbols  { include "pc+inet(evdev)+us"
                key <INS> { [ Overlay1_Enable ] };
                key <AE01> { overlay1 = <AE02> }; // Insert+1 => 2
                key <TLDE> { overlay1 = <I128> }; // Insert+~ => XF86LaunchA
            };
            xkb_geometry { include "pc(pc104)" };
        };
      
      Apply this layout: 'xkbcomp ~/ov.xkb $DISPLAY'.
      Run "xbindkeys -n -v"
      In the exact order:
      - press Insert
      - press Tilde
      - release Insert
      - wait
      - release Tilde
      Keyboard input in the new terminal window(s) would be locked
      until another Insert+Tilde .
      Reported-by: Mariusz Mazur's avatarMariusz Mazur <mariusz.g.mazur@gmail.com>
      Signed-off-by: default avatarMihail Konev <k.mvc@ya.ru>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      9d32b71c
  9. 02 Jan, 2017 6 commits
  10. 14 Dec, 2016 6 commits
  11. 13 Dec, 2016 1 commit
    • Adam Jackson's avatar
      Revert "damage: Make damageRegionProcessPending take a damage not a drawable" · 32e632e8
      Adam Jackson authored
      The commit message makes the assertion that the code below damage is not
      allowed to change whether there's a damage monitor for the drawable.
      That turns out not to be the case! exa's mixed code, at least, will
      create and destroy a damage in PrepareAccess. The destroy path can then
      be catastrophic, as damageRegionProcessPending will attempt to
      RegionEmpty memory from the middle of a freed block.
      
      I'd wanted that invariant for performance, but faster isn't worth
      broken, so revert it. I think what exa's doing is reasonable, so the
      better way to improve performance for the unmonitored case is to either
      revisit dynamically wrapping into the GC, or inline damage into dix.
      
      This reverts commit 4e124203.
      
      Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1389886
      
      Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      32e632e8
  12. 12 Dec, 2016 4 commits