1. 09 Dec, 2018 1 commit
  2. 27 Nov, 2018 1 commit
  3. 01 Jul, 2017 3 commits
  4. 03 Sep, 2016 1 commit
  5. 10 Apr, 2016 1 commit
  6. 30 Jan, 2016 1 commit
  7. 12 Apr, 2015 1 commit
  8. 01 Jan, 2015 1 commit
  9. 27 Nov, 2014 1 commit
  10. 24 Jun, 2014 1 commit
  11. 23 Apr, 2014 1 commit
  12. 15 Apr, 2014 1 commit
  13. 11 Apr, 2014 1 commit
  14. 06 Apr, 2014 1 commit
  15. 16 Feb, 2014 1 commit
  16. 25 Nov, 2013 1 commit
  17. 09 Jul, 2013 2 commits
  18. 20 Feb, 2013 1 commit
  19. 19 Feb, 2013 1 commit
  20. 26 Jan, 2013 1 commit
  21. 01 May, 2012 1 commit
  22. 30 Apr, 2012 1 commit
  23. 22 Apr, 2012 1 commit
  24. 20 Feb, 2012 1 commit
  25. 14 Feb, 2012 1 commit
    • Moritz Lipp's avatar
      Parse mouse events · 45c7be7f
      Moritz Lipp authored
      It is now possible to parse differnt type of mouse events (like mouse movement,
      scrolling or click/release of a button) in the following way.
      
      There are two new special identifiers
      
        scroll - Scroll event
        motion - Mouse movement
      
      that can be used in the following way:
      
        map <scroll> quit
        map <C-motion> quit
      
      If a button is used it is possible to pass the event type (default:
      button-pressed) to it by appending a string in the following form after the
      identifier:
      
        map <Button1> [mode] quit
      
      where mode can be one of the following options:
      
        button-pressed
        2-button-pressed
        3-button-pressed
        button-released
      45c7be7f
  26. 08 Feb, 2012 1 commit
  27. 25 Dec, 2011 1 commit
  28. 09 Dec, 2011 2 commits
  29. 07 Dec, 2011 1 commit
  30. 25 Nov, 2011 1 commit
  31. 24 Nov, 2011 1 commit
  32. 20 Nov, 2011 1 commit
  33. 12 Nov, 2011 1 commit
  34. 23 Oct, 2011 3 commits