Tony Zorman

On Wed, Apr 13 2022 18:03, Harjot Gill wrote: > I just spend an hour dealing with compilation errors with stack and > cabal methods. The GHCup method is indeed...

I suppose the easiest way would be to 1) resurrect #41 and its associated contrib PR and 2) rip "most" of #41 out of core and put it into contrib...

Well, at least it still seems to work:  Cleanup if definitely needed though (and much like the original reviewer, I also think that a lot of the core stuff...

At this point, does setting `_JAVA_AWT_WM_NONREPARENTING=1` (as, e.g., [javaHack](https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Util-Hacks.html#v:javaHack) does it) help?

We should probably also add a `Build using Nix` style section to [INSTALL.md](https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-xmonad)

> With the PatternSynonyms extension, it's possible to do this even more nicely and transparently. Rather than exporting `toMessage` I really like this idea :+1: I think we should go...

> Also, a quick bikeshedding question: Which do you like better: `doMessage`, `passMessage`, something else, or remove that from the pull request entirely to focus on the `SomeMessage` pattern synonym?...

On Thu, Sep 09 2021 09:08, wygulmage wrote: > For example, it would marginally simplify the message-handling code in > XMonad.Operations. Depending on how big of an undertaking this is,...

> A simpler fix would be to just change the serialization of type names in XMonad.Util.ExtensibleState, but I'm afraid that might slows things down: Most types used here will start...

Hm, I wonder if this use-case is general enough to justify implementing this as its own module?