Dear Laslo
Laslo Hunhold wrote:
> On Wed, 24 Jun 2020 14:39:03 +0200
> "Silvan Jegen" wrote:
>
> Dear Silvan,
>
> > The first beginnings are here (not by me):
> >
> > https://github.com/djpohly/dwl
> >
> > It uses the wlroots[0] wayland compositor library which a lot of
> > people may not co
On Wed, 24 Jun 2020 14:39:03 +0200
"Silvan Jegen" wrote:
Dear Silvan,
> The first beginnings are here (not by me):
>
> https://github.com/djpohly/dwl
>
> It uses the wlroots[0] wayland compositor library which a lot of
> people may not consider suckless however. I think the decision to use
> t
Hi
Anselm Garbe wrote:
> On Tue, 23 Jun 2020 at 14:48, wrote:
>
> [...]
>
> IMO the next evolutionary step of dwm will be considering to migrate
> to wayland at some point. X has always been a nightmare.
The first beginnings are here (not by me):
https://github.com/djpohly/dwl
It uses the wlr
On Tue, 23 Jun 2020 at 14:48, wrote:
> I am writing a wm for myself and I have a question about how dwm (and
> a lot of other WMs that copies dwm, such as katriawm and berry) hides
> clients.
>
> dwm manage() a client when it receives a MapRequest event and unmanage()
> it when it receives both a
I am writing a wm for myself and I have a question about how dwm (and
a lot of other WMs that copies dwm, such as katriawm and berry) hides
clients.
dwm manage() a client when it receives a MapRequest event and unmanage()
it when it receives both a UnmapNotify or a DestroyNotify event, while
hide
