Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Workaround for a bug in Chromium where it fails to attach a buffer to
the surface. Fixes #119.
|
|
|
|
Fixes #108.
|
|
Unlike with X window managers, the display socket in Wayland isn't set
up prior to starting the compositor. Because of this, you can't pipe
the compositor's output directly into a program which needs access to
$WAYLAND_DISPLAY, which is a typical setup for this purpose. Existing
scripts have been forced to create a pipe/FIFO or a temporary file as an
intermediary.
Instead, send the status info directly to stdin of the -s command, which
*does* have access to $WAYLAND_DISPLAY.
Fixes #103.
|
|
|
|
|
|
Fixes #102. The "ideal" behavior might be to ignore buttons other than
the one being used for the action, but this is super-simple and still
seems reasonable.
|
|
|
|
Merges #69.
|
|
Interface to display tag information on status bar
|
|
statusbar to printstatus
|
|
This reverts commit 1fa72b07728ebb396a9f236921b81c369bb12ccb.
Fixes #97.
|
|
|
|
Explicitly setting the handler for SIGCHLD to SIG_IGN tells the OS to
reap zombie processes automatically, which is what we wanted anyway.
|
|
conflicts with the statusbar outputs
|
|
|
|
|
|
|
|
This reverts commit 8ed88822ca4448b06c2d7e6155d8022152b78017.
|
|
This reverts commit a11f2bbc7a4068321767bd7e8c7eee1aee278bc9.
|
|
This reverts commit 67896e9d8b98f679faf4456e26e82057c1884789.
|
|
This reverts commit 0ff13cf216056a36a261f4eed53c6a864989a9fb.
|
|
|
|
|
|
|
|
monitor, and the focused client to a file for use by a status bar
|
|
Hopefully this will help "future us" understand what's going on.
|
|
This functionality belongs in updatemons(), where it can hopefully be
written a bit more elegantly.
|
|
The wlr-output-management protocol requires that either all of the
changes from an apply request be applied successfully, in which case a
"succeeded" event is sent, or all of the changes are reverted and a
"failed" event is sent. As written, this could partially commit
changes, then fail.
Test the changes first (even for an "apply" event), then commit or
rollback as appropriate.
|
|
This should end up firing precisely when we need to adjust our geometry,
rather than us guessing about it based on requests.
|
|
|
|
|
|
|
|
Fix Initialization of NetWM Atoms
|
|
Additionally, variables xcursor and xcursor_mgr are only used
when xwayland is defined, so I make the variables declaration
contingent on whether xwayland is being used
|
|
|
|
No need to track our own order; wlroots has a reasonable default for us
already.
|
|
Define monitor's x,y at compile time
|
|
Tracking with breaking change in swaywm/wlroots#2593.
|
|
Replaces the outputOrder patch.
This avoids recalculating positions and allows to arrange monitors in
any order, not just from left to right.
The order in which monitors are defined in config.h still matters but
it's just the order in the list, not the actual position.
|
|
This reverts commit 90cc3b1e2c824db74e932dbb9733d398619a037c. Didn't
mean to merge this change.
|
|
This is the order of *_destroy calls which resulted in the fewest
errors/leaks detected by Valgrind. Most of the errors come from the
gbm_allocator code - will have to figure out which destroy call is still
missing.
|
|
|
|
This was a prime candidate for reducing the verbosity of some of our
code
|
|
|
|
Similar to Linux kernel approach, encapsulate some of the uglier
conditional compilation into inline functions in header files.
The goal is to make dwl.c more attractive to people who embrace the
suckless philosophy - simple, short, hackable, and easy to understand.
We want dwm users to feel comfortable here, not scare them off. Plus,
if we do this right, the main dwl.c code should require only minimal
changes once XWayland is no longer a necessary evil.
According to `cloc`, this also brings dwl.c down below 2000 lines of
non-blank, non-comment code.
|
|
|