3 ms·
You can always write a configuration extension that takes $your_favorite_text_format into the data structure that configures xmonad. In fact, there is a text-b
by dons 15y ago
You can always write a configuration extension that takes $your_favorite_text_format into the data structure that configures xmonad.
In fact, there is a text-based configuration system (implemented on top of the full-language configuration system) that does as you describe in the contrib repo somewhere. You could also easily do e.g. JSON, or YAML or whatever.
And that's possible because we use a full language as the base layer. So "dumber" config systems can be layered on top without changing anything.
- pyre 15y agoI'm not arguing against the full language base layer. I'm saying that the op is complaining that he/she needs to learn Haskell to create an XMonad config. Even if I want to use one of those libraries, I still need to create an xmonad.hs file, and import the library. Vs having an xmonad binary that determines libraries/etc from a config file, and all code-level customizations are libraries/modules.