Heh. I used to write for the LG...

Some of the information is out-dated yes, you'd expect that. Especially when people were asking for help about dial-up modems, for example.

But I bet if you were to try some of the other stuff on there, it would still work today...

Correct. I've done no manipulation of the data that has been read in.

The bug is not present in the original LSM data (as I showed in another comment), but is present in the JSON data¹:

  {"author":"Manuel.Serrano@inria.fr (Manuel Serrano)","primary-site":"ftp.inria.fr /INRIA/Projects/icsla4048000 bigloo1.3b.tar.Z\n","maintained-by":"Manuel.Serrano@inria.fr","entered-date":"1996-01-01","version":"1.3","keywords":"","original-site":"","description":"Bigloo is both a interpreter and a compiler. It is conformantto IEEE Scheme standard with some extensions from which we can\nsite regular parsing or pattern matching.\n","copying-policy":"Copyleft","platforms":"","alternate-site":"","title":"\"Bigloo, a Scheme to C compiler\""}

You can see that the same bug is also affecting other multi-line fields, like “Primary-site” here, and “Alternate-site” for other projects.

1. https://xteddy.org/lsm/ajax_data.txt

Indeed. moxfm is the Motif version. See: https://bsd.network/web/@thomasadam/109378424501838841

The problem here is fvwm's features rely on server-side rendering, and I've not found anything equivalent for Wayland.

If there were, I'd be full-steam ahead with such a project. Probably using zig.

As it happens, there's bugger all. So it becomes a much larger undertaking if I'm to make a true port of fvwm to Wayland.

Expressed differently, everything will look and feel the same.

What a fucking shit show.

Wayland should die, and the so-called assumptions which lead to Wayland in the first place need re-evaluating.

This whole thing stinks.

That's because it was the Christmas holidays, and apparently, I have a life...

Things are being added now though.

Sorry, the point of my post was supposed to be "it's a new project and they're probably busy, hence one project conserved." Wasn't trying to disparage you at all.

Yeah. Nevermind though...

That's right, you can't send me patches as they're to be sent to the tmux mailing list. Is this not made clear already in the repository description?

I don't think GP was criticizing, just making a note of it.

Actually, I already provide this in the release notes. A PROTOCOL_VERSION bump means restarting tmux. We didn't do this between 1.9a -> 2.0, hence why it wasn't mentioned. Look at the release notes for 1.9, you'll see it was mentioned there. Simples.