I am not the author of dwl. Since dwl is based on wlroots (just like the popular Sway) it already supports making screenshots using grim and screencasts using wf-recorder.
You can try out dwl from within your current WM. The default modkey is Alt. If you want to use the Super key, change in config.h to and recompile. The default terminal emulator is kitty but you can change termcmd to alacritty if you want.
Currently, only native Wayland applications run on it. You can enable experimental Wayland support for Firefox with MOZ_ENABLE_WAYLAND=1, see Running programs natively under Wayland in Sway Wiki.
Do not hover over the edges of windows – this will crash dwl.
Hmmm, it says:
But dwm is not easy to understand and hack on, it’s terrible code with one and two-letter identifiers and sparse documentation that leaves you having to reverse-engineer it to understand it. Browsing this code it doesn’t look as bad on identifiers, but it’s still largely un-commented and requires reverse engineering to get any understanding of it.
One source file is definitely not a plus point, neither is limiting the lines of code, that just encourages people to use obtuse terse constructs over clarity. This one code file is a mass of unrelated functions and data structures just thrown together in one place for no good reason - presumably for people who find it challenging to work on more than one file at once?
These are things that chased me off dwm. It seemed like the bad coders’ idea of good code, and the whole “if you want an optional feature just apply a patch (and fix conflicts, etc…)” was utter bullshit too.
Sorry to be so negative, but dwm really rubs me the wrong way and I resent the time I wasted trying to live with it. This looks to have the same wrong-headed development aims. To each their own, if anyone likes it, good for them!