xmonad VS aur

If you want tiling, but i3 requires too much manual work, you might like the more managed layouts that are the default in XMonad: https://xmonad.org/

XMonad works fine with multiple monitors. Each monitor displays one of the many virtual desktops. The normal keys for desktops and for windows work pretty intuitively with multiple monitors.

Yes, depends on where you draw the line.

XMonad is a bit bigger: https://github.com/xmonad/xmonad

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.

I haven't used aura in a while, but as far as I understand the command sudo aura -Au --devel will only update packages that need updates based on if there are new commits upstream. As of aura 3.0.0 the git clones are kept in /var/cache/aura/vcs and when aura checks if the package needs an update it just does a pull on the repo and checks if the version is newer, so you will only see packages listed that require an update. You can add the --force flag to rebuild all of them, but that will generally do a lot of unnecessary work rebuilding packages with no updates upstream.

Yes, you need to use the CLI to run that, but it's trivial to do so and a real package management system brings many advantages over exe installers. The AUR, inspired by BSD's Ports, is one of the major advantages of Arch. It's very rare to find a package that isn't supported.

[1] - https://aur.archlinux.org/packages/radarr

[2] - https://github.com/fosskers/aura

Same here. Checked the github page and they're aware of it. Should be fixed soon. In the mean time I've been using aura. It's pretty great, should be more popular imo.

That's why I use aura

I found the discussion of the reasoning interesting: https://github.com/fosskers/aura/discussions/657

I've really enjoyed this one: https://github.com/fosskers/aura