Morgan Aldridge

I'll have to do some investigating on my end , but I'm also experiencing intermittent launch when activated via a left mouse click in a [`wmlaunchbutton`](https://github.com/phillbush/wmlaunchbutton) window, swallowed into the...

Thanks for reporting this, @TerminalHash. I'll need a little more information to try to triage this segfault, can you tell me what OS you're running `mlvwm` under, whether you installed...

> this segfault happens [if XCreateFontSet returns NULL here.](https://github.com/morgant/mlvwm/blob/8eb3738420093b8fc54ffe98eef2d60fb55e5f66/mlvwm/mlvwm.c#L101C22-L101C22) _Many_ thanks for your further investigation of this issue, @zulc22! Sometime around OpenBSD 7.2 or so, through 7.3, I noticed that...

_Note to self:_ I was most recently testing `picom` with `mlvwm` as follows: ``` picom \ -c \ --shadow-radius=2 \ --shadow-offset-x=0 \ --shadow-offset-y=0 \ --shadow-opacity=0.75 \ -f \ --fade-delta=5 \...

Interestingly, `"Open Location..." Action SendMessage C+L` works for Chromium/`chrome` under OpenBSD 6.4, so I'm not sure if it was just the other browser I was testing that wasn't working.

I'm not sure if I was accidentally preceding the line with "Menu" or what, but `SendMessage` has been working through OpenBSD 6.5 & 6.6. That said, it can sometimes be...

Re-opening this as @pierre-rs [pointed out](https://github.com/morgant/mlvwmrc/issues/4) that `SendMessage` is not working for ARandR under a number of OSes. I've confirmed under OpenBSD amd64/7.3-stable.

In a recent [discussion with Lucas de Sena and Thomas Adam on Mastodon](https://mastodon.social/@morgant/111185723514081990), I mentioned wanting to implement some sort of dynamic menu functionality (this issue). The next step here...

A further discovery made in the aforementioned Mastodon thread is that [FVWM has a `ReadPipe` function](https://mastodon.social/@morgant/111200677751356511). See [`ReadPipe` in the `FVWM` manual page](https://man.openbsd.org/fvwm#PipeRead). As mentioned, `mlvwm` doesn't support `Read` within...

This is related to Issues #45 & #47 in that it probably has the same type of memory leak. I'll have to double-check. Also, like #45 and considering the `fvwm`...