| Age | Commit message (Collapse) | Author |
|---|
|
Long overdue house cleaning.
The addition of compositing/monitoring overlays in vwm3 pushed vwm well past
what is a reasonable size for a simple thousand line file. This is a first
step towards restoring sanity in the code, but no behavioral differences are
intended, this is mostly just shuffling around and organizing code.
I expect some performance regressions initially, follow-on commits will make
more improvements to that end as the dust settles.
|
|
Major changes from vwm1:
- GNU screen-based "console" integration for monitored launching of X
clients via screen remote commands, replacing the simple double fork
approach used in vwm1. Clients exiting with non-zero status retain
their screen window in the console for 86400 seconds, facilitating
easier debugging and troubleshooting. The console xterm is accessed in
the shelf and has a red border by default.
- Xinerama/multihead support backported from vwm3, including the "screen
fencing" implementation facilitating screen-oriented window focus
cycling.
Shifting the Mod1-Tab window cycling focuses the next most recently
used window on another display. Unshifted stays confined to the
current display.
- SYNC extension integration for prioritizing the WM over other X clients
- setpriority() integration for "nicing" X client processes relative to
the WM process
- "autoconf" windows, horizontal/vertical halfscreen windows,
quarterscreen windows in addition to the full/all screen functions.
Mod1-[ and Mod1-] resize the focused window vertically with left and
right justification to half the screen in width. Shifting these does
the same thing just horizontally. Repeating the operation with a
second ] or [ press quarters the window in the respective screen
corner, extending upon the repeater pattern established in vwm1 for
full/allscreen windows with Mod1-k[k[k]]
- Exit now requires 3 consecutive strikes of Mod1-Esc
- Introduction of a README file
|
|
- Basic window management, window resizing, virtual desktops and shelf
implementation
- Simple double fork execution of launched clients
|
