test-ci-needs VS xmonad

Sorry, it was with `only:changes` and `needs`. Take a look at this issue[0] and this pipeline[1]. I've failed to find the failure mode in the documentation, so I suppose it may have been fixed since then - but we've developed an in-house workaround in the meantime that I'd trust a lot more than anything coming out from Gitlab.

--------

> A monorepo isn't "all but the most simple use-cases", it's usually a fairly complex usecase, and Gitlab have a myriad of ways to make monorepo CI easier - dynamic pipelines, remote triggers, includes, etc.

And every single feature you've mentioned here has a bug when combined with something else. That's the problem with Gitlab CI: everything works in isolation, but nothing composes properly.

Take includes: they don't work with anchors, so you couldn't have a generic template rules in the "main" file getting reused in the included files. This makes sense though! Anchors are a yaml feature. So gitlab added their own pseudo-anchors, called `extends`. You'd assume a smart, context-aware merge to happen, but no! Gitlab decided to go with a dumb object merge. Because the `script` step is a list of string, if both the parent and the child specify a `script`, only the child's will be used! Gitlab has a `before_script` step which can be used to workaround the issue for single levels of inheritance, but anything more complex ends up in a dead end. This feels like a feature that's been bolted on without any sort of design work.

[0]: https://gitlab.com/gitlab-org/gitlab/-/issues/31310

[1]: https://gitlab.com/ensc/test-ci-needs/-/pipelines/78713602

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