xmonad-contrib VS xmonad

This should now also be fixed in HEAD: https://github.com/xmonad/xmonad-contrib/commit/90f4a96f933a8ecc014b6def54fb929ee9e73e49

If you're on NixOS then definitely look into /u/LSLeary's excellent flake! (docs)

Perhaps you're not aware of the module exposed by the xmonad-contrib flake? It can do most of the setup for you. See the NixOS Modules section of https://github.com/xmonad/xmonad-contrib/blob/master/NIX.md.

Seems there was a documentation bug in that module. Does this fix help?

There is X.L.CenteredIfSingle. However, it didn't land in 0.17.0, so you'll have to either wait for 0.17.1 (dropping soon, I promise!), compile xmonad from git, or just copy the file as-is (which should be doable) into your configuration.

Btw there is an alternative way to implement smart bar using `AltMax` from xmonad-contrib but I'm not using it because of this [known bug](https://github.com/xmonad/xmonad-contrib/issues/75).

Note that the linked solution is a bit buggy (see here). But regarding your question, it's as simple as it gets. You could maybe replace (getModeName <$> (XS.get :: X ModeName)) with XS.gets getModeNameand maybe defining it somewhere else (e.g. logMode :: Logger), but that's really it. You could wait for #703 to be merged (whenever that may be), or just take the code from there (PSA: still in a rough state, undocumented, and very likely will change) and roll with it: it is xmonad after all, your config is going to be compiled anyway!

The official guide and the archwiki do say that it's okay to just install it via pacman, but I've also found some issues on the official repo that strongly suggest against installing via pacman and to use stack instead, as sometimes pacman breaks dependencies.

Especially Haskell tools often live in proximity to nix as well, e.g., pandoc or xmonad.

Hey everyone 👋 ! I'm currently working on a rust library for building and configuring your own shell! It's inspired by projects like xmonad and penrose where the configuration of the program is done in code. This means that for example, instead of using Bash's arcane syntax for configuring the prompt, it can be configured instead using a rust builder pattern! The project itself is still at a very young stage, so there are plenty of bugs and unimplemented features. However, some things that are (partially) implemented are:

Daily, because xmonad

If the problem is as described in the reply linked below, then this isn't a fundamental issue, but just a matter of how sendMessage is written. In fact, the fix already exists in xmonad/432:2fff2a0.

There are a few other things I could mention, but there are more like side issues, and not relevant to my actual LaTeX setup. First and foremost—and thus perhaps noteworthy after all—is bibliography management with arxiv-citation (see here for more words). This is integrated very well with the XMonad window manager, which makes it even more of a joy to use.

The tl;dr is that this is a bug in steam, see https://github.com/xmonad/xmonad/issues/423

And here is my Xmonad configuration