spwhitton

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?

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.

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.

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.

Should be possible to use Consfigurator for that, indeed.

One very cool usage for this is for security isolation. You run the web browser and this proxy in an isolated environment (e.g. a virtual machine) and then connect to it with an ordinary web browser from your regular workstation, possibly with another proxy in between that filters anything other than the clickable image map out.

You could still do multi-lingual content just by having it in separate .gmi pages and then linking between then. And your screenreader could follow links by embedding the text in the other language in the first page.

I agree with you that those behind Gemini should take this issue seriously, but maybe something like what I've mentioned is what they have in mind as their answer. Not sure.

Commenting on posts is something that Gemini enthusiasts are still figuring out. Currently people post Re: posts to their own gemlogs and then mail a link to the person who made the original post, but I think they are hoping to have a less effortful convention.

They've tried to make it really difficult, though -- for example, how there is only one type of request.

Extending text/gemini is more feasible indeed.

Sorry to put you through that! I normally go back and edit my blog posts at least a little bit, but I wasn't very happy with this one, so I didn't bother. I didn't expect it to have a readership beyond whoever happened to look at planet.debian.org yesterday.

One of the two main web-to-Gemini proxies can already do this and the gmi2email script I wrote does it too. I think other clients probably can too.

Yes, this really bothers me too. Title, sections, subsections and subsubsections is not too much sectioning.

There's already a git repo for every package.

    % apt-get install dgit
    % dgit clone foo-package