Chris Siebenmann

A third oddity: the return value of `_prev_weed_is_expose()` appears to be mismatched with the value that `FWeedAndHandleIfEvents()` expects, because FWeedAndHandleIfEvents uses `_fev_pred_weed_if()` as its predicate function, which seems to have...

I will see if I can understand this code well enough to create a patch that won't subtly break everything, but I'm not certain I will be able to. The...

I'm currently running a fvwm3 built with this frankly terrifying hack patch and it hasn't exploded and doesn't seem to have any of the expose issues. Given the code duplication...

Some comments. First, I have to correct myself about FCheckPeekIfEvent(); it always returns the first matching event, skipping all the rest of them. This means you could use it to...

My patch from January (in the comment above) continues to work for me without problems.

To extend on @ThomasAdam 's answer, the trigger condition for this issue in fvwm3 was a change made in Xlib/libX11 1.8, where they decided to insist on thread safety even...

One thing that currently makes this unpleasant is that if you use 'Clear selection' to see everything and then refresh the page, it usually goes back to only showing a...

I am also seeing this on Fedora 40 with their 6.8.9-300.fc40.x86_64 kernel and the current ZFS git tip. The comments in the source code suggest that `mzap_ent_phys_t` is variable sized,...

I am using Fedora 40 with (currently) kernel 6.9.9-200.fc40.x86_64, with what is currently the git tip development version (2.2.99-560_gaea42e137) and I see these sa.c assertions. I see them in three...

The first two warnings trigger during system boot as my pools are imported and filesystems mounted. The third triggered slightly later, when I logged in and started various programs as...