default CC to gcc

posix c99 does not accept `-pedantic`

Fixes: https://codeberg.org/dwl/dwl/issues/584

Check for null monitor in resize function

Add output to layout after enabled state is committed

fix: make sure selmon doesn't get set to disabled mon

Run startup_cmd in new session and kill the entire group

When a user's startup_cmd is a little more complex, e.g. a shell script,
and forks off several processes, then killing only the main child pid
might leave unwanted processes behind on exit. Not all children will
notice when their parent or the compositor has quit.

To fix this, put startup_cmd into its own session and process group, and
kill the entire group on exit.

Make sure toplevel_from_wlr_surface is called with a valid surface pointer

minor adjustments in Makefile

use tabs in client.h

Fixes 298949bbc4eae8cedb9cdd11cfc9ebd139ac5d5f.

make sure clients share the same layer on floating layout

create a keyboard group for each virtual keyboard

Allow negative coordinates in MonitorRules

Monitor/output position (-1, -1) remains as a single indicator value for autoconfigure layout.
Additionally, one minor comment typo is corrected.

Replicate dwm behavior for sloppyfocus

dwl-patches overhaul - doc changes

Update wmenu-run name

switch to wmenu

bemenu is very bloated, turning itself into a library, which makes it
7489 SLOC.

wmenu on the other hand, looks suckless by default, and is only 2000
SLOC, which i also find alot nicer to use, since bemenu does nothing
to replicate the original dmenu feel.

put wlr_layer_shell top layer below fullscreen

fixes wlr_layer_shell top clients showing over fullscreen clients

do not set withdrawn state for xwayland clients

Closes: https://codeberg.org/dwl/dwl/issues/573

properly resize on configurex11

Fix rule examples; minimize newbie surprises

Make example rules be actual EXAMPLES.
Now newcomers should not have to ask, "When I start firefox, nothing
happens. What is going on?"

Also clarified a minor typo and a consistency in spacing.

fix virtual pointers

When motionabsolute() is called from warpd, event->time_msec is 0, so
motionnotify() doesn't call wlr_cursor_move(). Fix this by explicitly
warping the cursor in this case, like it was done before implementing
pointer constraints.

I don't know if this is a bug in warpd or time_msec is always 0 with
virtual pointers, since the only other software that uses the virtual
pointer protocol I know of is wl-kbptr, and I can't get that to work
with dwl at all.