| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
which one may configure (wm <name> <path_and_args>) (and choose) specific
window managers to replace the running one. 'wm cwm cwm' is included by
default.
No objections and seems sensible to sthen.
|
|
|
|
|
|
|
|
|
| |
into the keyrelease event, only performing what's actually needed for each;
should result in much fewer events against keyreleases. No intended behaviour
change.
Additionally, like we do for group membership, grab the keyboard only when
required for cycling.
|
|
|
|
| |
border work for a group/ungroup action.
|
| |
|
|
|
|
|
|
|
| |
close to cwm's 'ignore'.
Roughly based on an initial diff from Walter Alejandro Iglesias, but with
support for both Atoms and without cwm-based bindings.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
re-proposed by Julien Steinhauser with an updated diff. Apparently this was in
the original calmnwm.
However, expand the original idea and let clients 'snap' to edges instead,
neatly allowing key bindings that snap to adjacent edges (i.e. corners) as
well. No default bindings assigned.
|
| |
|
| |
|
|
|
|
|
| |
a wrapper so that the key and mouse based move/resize callbacks can be unified.
This has already been done with other window operations and menus.
|
| |
|
|
|
|
| |
greatly simplifies upcoming work.
|
|
|
|
|
|
| |
actions, so as to not lose windows off the edge.
inspired by diffs (and feedback) from Vadim Vygonets.
|
| |
|
|
|
|
|
|
| |
While
here, normalize the remaining search_print_* argument paramters.
|
|
|
|
|
| |
change now, though more can likely go later, losing the (paritally complete or
incomplete/broken) argument completion bits.
|
|
|
|
|
|
|
|
| |
the previous behaviour of 'menu-window'. 'menu-window' becomes the default
binding; use 'bind-mouse "1" menu-window-hidden' to restore old behaviour for
those who prefer.
OK sthen@ (long long time ago on a different version)
|
|
|
|
| |
naturally.
|
|
|
|
| |
mouse bindings.
|
| |
|
|
|
|
|
|
| |
client search as different potential str matches are cycled through. If there's
interest, the only string that doesn't exist in the listing is the window's
class - that can be added of course, but it makes the line too long imho.
|
|
|
|
|
|
|
|
| |
client_ctx in keypress and buttonpress event handlers; pass appropriate *ctx's
based on context.
While here, limit some globals, replace defines with appropriate variables and
fix some naming.
|
| |
|
| |
|
|
|
|
|
|
|
| |
key press. This allows to remove a few hacks to duplicate functions only
for behaviour changes; now differing behaviours are pushed down to the
callback. Also will allow for previously unavailable actions to be bind-able
down the road.
|
| |
|
|
|
|
|
|
| |
the screen; adapted from an ancient diff from Sviatoslav Chagaev. Things
in this area will likely change, but put this in so it works now and
serves as a reminder.
|
|
|
|
| |
needed/used.
|
| |
|
|
|
|
| |
needed.
|
|
|
|
| |
well as give 'sticky' groups its own variable.
|
| |
|
|
|
|
|
| |
the one line wrappers provided no value and limited altering calls where
needed; additionally, most of them had but one caller.
|
|
|
|
|
|
|
| |
lists; use it appropriately for both window dimension and position in
the respective mousefunc calls.
ok bryent@
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
active; while we already look at what's under the pointer, use this
information first, then look under the pointer (saving that round-trip).
This restores the active state to a client after restart even if the
pointer is not above it (and of course the pointer is not above another
client).
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|