| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
macros in the one place they are needed.
|
|
|
|
| |
holding a command name limit as well.
|
|
|
|
| |
removes limit on name matching.
|
| |
|
|
|
|
|
| |
user visable changes at this point, but they'll merge at an appropriate
time.
|
| |
|
|
|
|
|
| |
struct, binding; they were essentially the same accept for what was
'pressed', keysym or button.
|
|
|
|
| |
command name - last match.
|
|
|
|
|
|
| |
config parse (and use conf_cmd_add to populate defaults); based on a
discussion with Tiago Cunha. While this looks ugly, there are likely
some other changes here to come.
|
|
|
|
| |
config parse; based on a discussion with Tiago Cunha.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
bits even closer.
|
|
|
|
| |
rcyclegroup wrapper need - now similar to kbfunc.
|
| |
|
|
|
|
|
|
|
|
|
| |
- make conf_bind_kbd return error on non-matches to match what
conf_bind_mouse does.
- rename some variables while here for clarity.
- constify bind and cmd.
from Tiago Cunha.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
| |
ewmh hint; urgencyborder is configurable. The urgency flag will stick,
even while on a client in a non-viewable group, until the client
receives focus (where the border is reset). Initial diff from Thomas
Adam with some changes/enhancements from me.
|
| |
|
|
|
|
|
|
|
| |
worked (and no one complained!). While it's fairly easy to fix, users
should be using keysym names and not keycodes.
Discussed at length months ago with todd@, matthieu@ and Owain.
|
| |
|
|
|
|
|
|
|
| |
BadValue) when the modifier is already AnyModifier . Instead alter
xu_btn_ungrab() to ungrab AnyButton/AnyModifier and call it only when a
client is coming into focus in client_setactive(), instead of iterating
over ignore mods - matches how we handle key grabs.
|
| |
|
| |
|
| |
|
|
|
|
| |
for gathering Atoms.
|
| |
|
|
|
|
| |
bound by default.
|
| |
|
| |
|
|
|
|
| |
from Tiago Cunha
|
| |
|
|
|
|
| |
of the screen (quick fix); discovered the hard way by Rodrigo Mosconi.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
to grab keys in keybindingq. we don't need to ungrab/grab on every
addition to the queue, just once with a complete keybindingq; simplify
grabbing keys per screen (during init) and during a MappingNotify.
while here, change conf_grab_{kbd,mouse} to require only a Window.
|
|
|
|
| |
here; just build keybindingq.
|
|
|
|
| |
config options, add the keybinding GrabKey calls here
|
|
|
|
|
|
|
| |
validity during the parse phase and not bother adding it to the queue,
instead of each time a client needs to grab (when it's too late);
furthermore, make this a config error, stop parsing and load the
default config.
|
|
|
|
|
| |
the menu window since that's the only place on which we draw
- elminate the need to change the drawable on every font draw
|
|
|
|
| |
config parameters.
|
|
|
|
|
|
|
|
|
| |
- merge border/menu color structures/functions since they now both use Xft
- switch xu_xorcolor to operating on XftColor instead of just
XRenderColor (basically adding pixel)
- if color name allocation fails, revert back to default (this, along
with font validation should occur during config parse, but we don't
have screens setup yet - likely to change at some point)
|
|
|
|
|
| |
configuring the screen *after* parsing, just as we do a conf_client on
client manage.
|
| |
|
| |
|
| |
|