aboutsummaryrefslogtreecommitdiffstats
path: root/kbfunc.c (follow)
Commit message (Collapse)AuthorAgeLines
* For both kb and mouse move, it is possible to grab a client and move itokan2016-10-03-2/+14
| | | | | completely off the screen/region; instead, if the pointer is outside of the client bounds, warp the pointer to the closest edge before moving.
* client_ptrwarp should not deal with unhiding or raising clients (non ptrokan2016-10-03-1/+3
| | | | | requests); most callers do this already - deal with the few that do not. client_ptrwarp becomes a simple wrapper (setpos) but it will be expanded.
* Continue merging kb and mouse functions: foldokan2016-09-22-8/+23
| | | | | | mousefunc_menu_{client,cmd,group} into the respective kbfunc_menu_{client,cmd,group} functions; simply pass a flag down from config denoting mouse action behaviour.
* If a client does not set increment values, use 'moveamount' as a way tookan2015-11-17-8/+10
| | | | | | scale keyboard based resizes; extend kbfunc_amount(). Behaviour noted by, tested by, and ok sthen@
* more client vs screen context differencesokan2015-11-12-5/+5
|
* If a client sets hints, honor them for kb resize requests, just like weokan2015-11-12-5/+5
| | | | | | do for mouse based resize requests. Based on a patch from Vadim Vygonets.
* Move kb pointer movement out of the kbfunc_client_moveresize since it'sokan2015-11-12-76/+93
| | | | | | | | got nothing to do with clients, thus doing flags work causes lots of waste and almost useless jumpy pointer movements; while here, split out move and resize since they share almost no code, just like mouse client move/resize; factor out amount and factor. Still wonder why this is here, but it works now.
* Partial revert of replacing screen_area() with region_find(); until aokan2015-11-11-6/+7
| | | | | | fix for a regression is found; this bug has been around for a long time it seems, but this change exposed it. Likely need to track clients in to and out of regions.
* Use position on root to figure out region.okan2015-11-10-4/+3
|
* Start cleaning up name vs function differences; replace magic numbers.okan2015-11-10-18/+18
|
* Extend region to include both view and work areas; switch tookan2015-11-09-6/+6
| | | | | | | region_find() which no longer needs to recalculate gap each time a client (or menu) is created or altered. If no RandR, fall back to display dimensions while building regions instead of during execution.
* On execwm, we should properly release resources before exec'ing into aokan2015-09-16-3/+4
| | | | | | | new window manager; so allow CWM_EXEC_WM to assign new wm to wm_argv and pass through cwm_status (now EXECWM) so that x_teardown() gets called before exec'ing the new window manager. Removes the need for a separate x_restart() now, using new wm_argv; and consolidates errno for execvp.
* Lost fix from r1.112; add comment.okan2015-08-28-2/+3
| | | | Reported (again!) by Peter Kane.
* Move client cycle grab/ungrab into a more relevant place; while here,okan2015-08-27-9/+3
| | | | update comments about why we need to grab/ungrab the keyboard.
* _NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan2015-08-21-2/+2
| | | | position and size; based on discussion with a few.
* Instead of special casing the 'term' and 'lock' commands, go back tookan2015-08-21-3/+7
| | | | keeping them hidden; showing them has apparently caused confusion/angst.
* introduce 'groupsearch' for group menu search; matches on either groupokan2015-07-12-1/+26
| | | | number/shortcut and/or name.
* revert previous; seems search_match_text() needs mi->text pre-populated.okan2015-07-03-2/+2
| | | | | | (only used in one place, application menu searching); re-visit later. broken application menu searching reported by Peter Kane.
* no longer need to pass down format strings after introducing search_print_cmdokan2015-06-30-2/+2
|
* Introduce a callback for cmd menu printing, special-casing 'lock' andokan2015-06-30-2/+2
| | | | 'term'.
* Shuffle code in kbfunc_ssh so that a missing known_hosts file stillokan2015-06-29-8/+7
| | | | | | allows a (now blank) menu to appear, as opposed to nothing at all. Behavior reported by Alex Greif.
* Mechanical change from xinerama to region backed areas.okan2015-06-26-5/+5
|
* just populating the ctx is enough since the menu uses a callback and ignores ↵okan2015-06-08-2/+2
| | | | anything else
* merge kbd and mouse grouptoggleokan2015-05-21-4/+6
|
* Switch to limits.h; replace MAXPATHLEN and MAXHOSTNAMELEN with PATH_MAXokan2015-01-19-5/+6
| | | | | | and HOST_NAME_MAX+1, respectively. ok doug@
* these have nothing to do with 'sticky', but rather group membership; rename.okan2014-09-27-2/+2
|
* these client actions are just toggles; less confusing with better namesokan2014-09-17-13/+13
|
* ewmh states _NET_WM_STATE_STICKY should not alter positionokan2014-09-17-2/+2
|
* Remove incorrect cast in kbfunc_exec. In kbfunc_ssh, reverse logic onokan2014-09-11-5/+5
| | | | truncation check so it's obvious.
* Remove duplicate client queue (mruq); instead, remove and take theokan2014-09-08-2/+2
| | | | | | global Clientq and place it inside screen_ctx since every client belongs to a screen, then use the same per screen clientq to track stacking order (the sole reason for mruq).
* Few style nits; extend 'path' to MAXPATHLEN.okan2014-09-06-11/+14
|
* Move termpath and lockpath into cmdq; side effect is that 'lock' andokan2014-09-06-4/+17
| | | | 'term' now show up in the application menu.
* add explicit paran and drop some empty lines bringing like functions closerokan2014-09-01-2/+1
|
* Implement _NET_WM_STATE_STICKY, bound to CM-s by default; allows anyokan2014-08-25-1/+7
| | | | | | | client to 'stick' to all desktops (ewmh speak) or groups - this currently has the same affect as setting a client's group to 'nogroup', with the exception that the client can also be in a group, so when un-sticking, the client will go back to its original group/desktop.
* Move cwm_status around to avoid header fu, and remove extraneous signalokan2014-01-30-1/+3
| | | | header from xevents.c; noticed by Christian Neukirchen.
* Minimize trivial differences between a few kb and mb functions.okan2014-01-29-2/+2
|
* If no title is supplied, term uses only the basename for its title.okan2014-01-23-3/+3
| | | | | | | This is useless when searching for windows launched via the ssh command menu; supply a more useful title: '[ssh] <hostname>'. Idea from todd@, ok todd@
* zap whitespaceokan2014-01-22-26/+26
|
* Somewhat streamline event loop/restart/quit handling; most notableokan2014-01-22-13/+3
| | | | | | | | change allows a restart to trigger proper teardown first, even though teardown is not (yet) complete. After some discussion with oga@nicotinebsd.org regarding a more complicated version/idea.
* Sprinkle a few more const; from Tiago Cunha.okan2014-01-21-2/+3
|
* Save the ptr position before lowering via kbd, so as to be able to cycleokan2014-01-20-1/+2
| | | | | back with the pointer in the right place; matches behaviour when lowering via the mouse function.
* constify and rename some confusing variables around cmdq.okan2014-01-20-3/+3
|
* Add a function that adds an entry to a menuq, normalizing a common codeokan2014-01-20-24/+8
| | | | path; from Tiago Cunha.
* use consistent typesokan2014-01-03-2/+2
|
* Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan2013-12-16-1/+7
| | | | | | | | | | | | | | | | Since we already have a form of 'maximize', we need to differentiate between 'maximize' and the new 'fullscreen' mode. The 'maximize' mode will continue to honor gap but now *retains* the border, matching the 'vert/horz maximize' behaviour. The new 'fullscreen' mode supports and follows the _NET_WM_STATE_FULLSCREEN hint, allowing the client perform additional window modifications; in this mode, cwm(1) will *ignore* gap, remove borders and freeze(move/resize) the client. Additionally, 'fullscreen' mode will remember various combinations of previous states. * default keybinding changes: CM-f 'fullscreen', CM-m 'maximize' (re-map as desired). Positive feedback from a few, testing and ok sthen@
* Teach screen_find_xinerama() to apply gap only when told to do so;okan2013-12-13-2/+2
| | | | adjust callers. Needed for an upcoming feature.
* Instead of using work area, use the Xinerama area for snap calculations;okan2013-12-13-3/+7
| | | | based on a patch from Thomas Adam with appropriate adjustments for gap.
* Make sure we really take work area gap into account with snap calculations;okan2013-12-12-3/+3
| | | | from Dominik Honnef via Christian Neukirchen.
* like gap, make snapdist per screenokan2013-11-27-3/+3
|
* a few err->errx since we don't have error messages here; from Tiago Cunhaokan2013-10-17-3/+3
|
powered by cgit and git | oriole.systems | how to verify signatures