Matthias S. Benkmann

It's an unfortunate side effect of the coarse nature of the patch.The ideal implementation would be to grab exactly those Button+Modifier combinations that are necessary due to the configuration. In your case that would be Button1+Alt. Unfortunately the Fluxbox grabbing code isn't easy to understand, so I wasn't able to do the fine-grained solution. For you personally, you can simply change the patch so that in the function ungrabClickToFocus() after the XUngrabButton()... you add a XGrabButton(display,Button1,Mod1Mask,frame().window().window(),True,ButtonPressMask,GrabModeSync,GrabModeSync,None,None)...

I uploaded the fix under Patches.

Fix the bug #1187 (Chromium-based apps misbehave)

nmark,abort has side effects

I analyzed this and fixed it in my tree. I went to fluxbox.org to see if there is maybe a github repository I can send a pull request to. Turns out there's still only links to this Indian site and you can't even find the address of the git repository, not to mention instructions on contributing. It is sad to see a window manager that I've used for so long rot away like this.

Sorry for spamming this unrelated bug but I've been googling for a while already after trying ChatGPT to get the Ctrl-C behavior fixed and the above comment from years ago is the only thing I found. I NEED CTRL-C TO EXIT EVEN WHEN THERE IS A MARK. I just upgraded from Ubuntu Focal to Noble and this behavior change is KILLING ME. I tried changing the definition of ^C to "nmark,abort" but while that works in the main text screen it breaks Ctrl-C for instance in the "Lose changes to this file (y,n,^C)"...

Sorry for spamming this unrelated bug but I've been googling for a while already after trying ChatGPT to get the Ctrl-C behavior fixed and the above comment from years ago is the only thing I found. I NEED CTRL-C TO EXIT EVEN WHEN THERE IS A MARK. I just upgraded from Ubuntu Focal to Noble and this behavior change is KILLING ME. I tried changing the definition of ^C to "nmark,abort" but while that works in the main text screen it breaks Ctrl-C for instance in the "Lose changes to this file (y,n,^C)"...

The technical side is not the issue. The important thing is that you're not opposed to the concept. If you said that you oppose the change from duration to explicit note offs in principle, I wouldn't start working on it.