Yeah, that's what I used to do, basically, before writing papersway. I was happy with it for many years.

It works by interacting with Sway's IPC API. (Or i3's IPC API.)

papersway has a toggle like that :)

I (the author) have been using it for several months now and haven't really experienced any dissatisfaction.

Also https://spwhitton.name/tech/code/papersway

Thanks for posting my project.

I have been using this for a couple of months now and I no longer get yanked out of a flow state when I have lots of windows open. Window management has truly faded into the background, which wasn't the case for me with Sway/i3wm before now. So I'm quite pleased.

I think others might like it too.

I transferred all my Sieve rules for marking mail as read to Gnus scoring rules, but haven't made much progress beyond that. I turned on adaptive scoring, but I'm not convinced it is achieving anything. How do you make scoring useful, assuming you do mean more than just the equivalent of Sieve mark-as-read rules?

I mostly use permanent rules to increase the score of reputable contributors to the kernel mailing lists, maintainers, etc. I also use a mixture of permanent and temporary rules to increase the score of things I want to follow or decrease for things I want to ignore. Oh and I lower the score of replies, which has the effect of de-emphasising them unless they’re part of a thread that has an increased score.

It's interesting that this user was using notmuch before Gnus. I switched notmuch.el+notmuch to Gnus+notmuch last year, i.e., I kept using notmuch but I switched from notmuch's own Emacs frontend to Gnus's support for notmuch.

It takes Gnus ten minutes to start up even with nativecomp, and hours to do its initial indexing (but you already have to give up that time for notmuch's own indexing). It's unusable without nativecomp.

I switched because I realised that I was hackily reimplementing many Gnus features and ideas on top of notmuch.el in my Emacs init. I had to fix some bugs in Gnus, and help the author of nnselect fix some much harder bugs, over the past nine months. It works well now.

Wow. For me, Gnus starts in <10s. But I guess it depends a lot on what backends you use (I use dovecot+mbsync for mail, so Gnus doesn't really index anything)

Ha, Emacs, sbcl and gcc are exactly what I've been using for development for the past few months on my Raspberry Pi 4 desktop replacement.

If you have two raspi, 4GB and 8Gb models, you can use tmux, btop to check your memory and cpu levels.

Consfigurator relies on homoiconicity for starting up Lisp images on remote hosts and giving them instructions. The user's specification of what configuration to apply to a host is basically just Lisp code and this can be trivially serialised and deserialised.