This reverts commit 3a72cd9.

There is probably an easier way to keep this difference, but hey, this
works for me.

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 djpohly#103.

Fixes djpohly#108.

Add uninstall target in makefile like dwm

Workaround for a bug in Chromium where it fails to attach a buffer to
the surface.  Fixes djpohly#119.

Wait until map to set window's tiled state

before set tiled verify if client is xdg-shell, then set tile

Along with starting the -s command earlier, this will allow the initial
monitor setup to generate printstatus info.

If a transient failure occurs in wlr_output_commit, re-render until it
doesn't happen.  This could possibly be removed if we decide to
implement damage tracking in the future.

It seems like there are people trying dwl who aren't as familiar with
how their distros do development, so let's give them a pointer in the
right direction.

Includes mention of video/input groups

…g called on every frame when things like dmenu are up

This lets applications, such as mpv with --video-sync=display-resample,
know accurately when frames are displayed and ensure smooth video
playback.

This allows clients to disable idle monitoring

die() replaces EBARF and BARF
and allow us to add `-pedantic` to CFLAGS

to fix compile errors with `-pedantic`

Check the wlr_layer_surface_v1_state.committed bitmask to see if we need
to rearrange. This is also what sway does.

Without this check, every commit request (even if only the attached buffer
changed) will lead to another configure event, which will lead to another
commit, etc.

This loop results in swaybg consuming 100% CPU.

Co-authored-by: Owen Rafferty <[email protected]>

The x/y fields in monitor rules are unused and were meant to be deleted.
Also removes the outdated comment in config.h.

This causes all Xwayland clients to be treated as floating