Tony Zorman

Will close as "not reproducible"

And that's why X.H.DynamicProperty exists. I do also think that trying too much to compensate for programs blatantly breaking standards will only lead to a lot of headaches

I'm going to reopen this in the interest of "let's not forget to properly document this at some point". For what it's worth, I like `onXPropertyChange` as a name!

It is true that we have different scratchpad implementation, but I don't think I have ever seen someone use anything but X.U.NamedScratchpads (plus the loggers). I'm sure these people exist,...

> Well I agree in the sense that I think it makes sense not to deprecate the module, but I do think an aggresive refactor is order. I believe that...

I will close this for now, as the title of the issue ("3 Different Scratchpad Implementations; 2 Scratchpad PRs") has been dealt with. If we want to discuss the possibility...

Have you tried using [X.A.CycleWorkspaceByScreen](https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-CycleWorkspaceByScreen.html)? The docs are pretty bad, but what you are supposed to do is something like ```haskell import XMonad.Hooks.WorkspaceHistory (workspaceHistoryHook) import XMonad.Util.EZConfig (additionalKeysP) import XMonad.Actions.CycleWorkspaceByScreen (cycleWorkspaceOnCurrentScreen)...

Yes, contributions are always welcome and these modules look quite nice! A few suggestions for making PRs: > * [XMonad.Layout.PseudoTiling](https://github.com/Procrat/xmonad-pseudotiling) which lets windows have their preferred size (within the limits...

That's exactly the part I'd like to have some clarification on, yes :)

Thanks, these are good points. I pushed some thoughts in a80f7532018ad2fc7d94826544fc0ee3c4f37963 (docs TBD). > * Those three key config values are duplicated in the standard config, so we could provide...