1. Jun 14, 2020
  2. May 11, 2020
  3. Mar 18, 2020
  4. Feb 07, 2020
  5. Jan 05, 2020
  6. Nov 06, 2019
  7. Aug 14, 2019
    • okan's avatar
      cvsimport · 4154b9b1
      okan authored
      * refs/heads/master:
        Because cwm warps the pointer during a client move (to stay within the client), there's a window of time where an expose or enternotify event will get generated for a lower client; use a hammer and drain events after keyboard move/resize, until such a time that cwm doesn't warp the pointer.  Behavior noticed by kn.
        Fix regression from r1.107 (lost a return); kettenis@ pointed out the high potential for a use-after-free (true!) where kn@ ran into the regression using an app that actually exercised the XGrabPointer() failure path.
        Add application section
        command uses execvp(3) not execve(2)
        Plug a memory leak in log_debug(); OK okan@
        Handle _NET_WM_NAME changes.
      4154b9b1
    • okan's avatar
      Because cwm warps the pointer during a client move (to stay within the client), · 781af9c9
      okan authored
      there's a window of time where an expose or enternotify event will get
      generated for a lower client; use a hammer and drain events after keyboard
      move/resize, until such a time that cwm doesn't warp the pointer.  Behavior
      noticed by kn.
      
      ok kn@
      781af9c9
  8. Aug 12, 2019
  9. Jul 10, 2019
    • kn's avatar
      Add application section · fdb841c3
      kn authored
      Link what is described as "applications" here to how they are actually
      defined in cwmrc(5).
      
      While here, call the configuration file what it is instead of reusing
      the default path (already mentioned in the FILES section).
      
      OK okan
      fdb841c3
  10. Jul 03, 2019
  11. Apr 30, 2019
  12. Mar 11, 2019
    • okan's avatar
      cvsimport · 85d88f33
      okan authored
      * refs/heads/master: (23 commits)
        Check the atom type on propertynotify before iterating.
        use screen_find() for xrandr crtc changes
        Find the managed screen from the parent window for client_current().
        Print window id in hex; while here, remove unnecessary newline.
        Similar to keypress event, fetch the screen from the event root window in the buttonpress handler; bail if we don't manage the screen. Allows us to find the current client based on the screen/event root.
        extend verbose logging for key/button events
        [keypress event] turns out we've been checking the wrong window for a matching client thus always falling back to client_current(); while the current client is problaby right in most cases, use event's subwindow (not window) to find the client. Bail early if this event came to us from a screen we don't manage. This is result of us grabing all keybindings off the root window instead of selectively.
        add parans for readibility
        Teach client_current() to use a screen to find the current client instead of iterating over all (fallback if no screen provided for now). Initially convert trivial uses of client_current().
        check cc->gc directly
        zip extra lines
        gc clientq inside groups, instead use the better maintained one per-screen
        shuffle deck chairs: rename group actions to match intent for clarity
        same thing as screen_find()
        Separate out the menu window from the client resize/move geom window; in each case, create and destroy on-demand. Isolate more menu specific code.
        fix a few misplaced (and misnamed) ewmh root window functions
        _NET_WORKAREA needs ngroups, so screen_update_geometry() needs to come after conf_group().
        simplify xftcolor config
        Tie group number and name together during config.
        Move the group index (desktop number) check to the only 2 callers that require checking due to ewmh.
        ...
      85d88f33
    • okan's avatar
      9a7528f5
    • okan's avatar
      use screen_find() for xrandr crtc changes · e55c0d48
      okan authored
      e55c0d48
    • okan's avatar
  13. Mar 09, 2019
  14. Mar 08, 2019
  15. Mar 07, 2019
  16. Mar 06, 2019
  17. Mar 05, 2019
  18. Mar 04, 2019
  19. Mar 01, 2019