If you :flag a message and then you try to filter with :filter -x flagged it won't show it. What it shows for me looks like the messages which was flagged at some point of the time, but it's just a guess, but the result of the query is not empty, that's what I'm saying.

Everything works as expected without notmuch with just maildir.

When entering viewer ([view]), I'd like to see the flags, like Flagged(! mark on the message in message list) and so on.

The use case is to not toggle flag on already flagged message.

On irc it was suggested that the following could be done

rockorager |  We could add a "header" field that is the same as the flag field in the message list

If you have multiple accounts and click on one the right side(one or 2 cells of offset usually, but I feel like it's more like 64 * tab_idx, but that's a guess) of the first one in a tab bar, you'll get on the one to the right instead.

aerc version: 63019343660049eadb2273a7ea0e13a2a0580b51

The issue is not present with v0.14.0 so it was a recent regression.

It was suggested on aerc that it has something to with template PR.

I do have the in aerc.conf

tab-title-account = "{{.Account}} {{if .Unread}}({{.Unread}}){{end}}";

The bug is unique to kitty terminal + aerc terminal interactions. The bug is not present when colorize script is used outside of the aerc terminal.

The bug can only be reproduced inside the kitty(tried alacritty and foot) so I'd say it's just a kitty bug which should be reported to it.

Though, given that it doesn't happen outside of aerc-terminal, it could be something with it, cc ~rockorager

When sending pgp signed mail the resulted signature ends being broken. It was suspected that the issue is with migadu, but neomutt manages to send everything correctly and further research showed that the issue is within aerc.

See https://github.com/emersion/go-message/issues/165#issuecomment-1447024320

Versions tested: 0.14.0 and c29d08808986dbf19df498b9ee9c4887146266dc

I've sent sample emails to ~rockorager from both aerc and neomutt.

If you run w or who after you've logged in you won't get any users logged in.

To make those commands work greetd should update wtmp/btmp/utmp, etc

On HiDPI output(scale 2) the background image is just a top left corner of the original image.

I wonder if this was caused by 5b1bb83b1454507e80336c4696df28170b9bb18d.

Well, if we take into account information about 14 days, the patch was way before this, like ~40 days ago, so it was running at least for near a month applied, before the mentioned breakage.

Also, I'd like to mention that travis is using the exact same scopes as a dispatch.sr.ht, so I don't think it needs more permissions, since the amount of permissions travis is using should be enough to do that. public_repo is a bit draconian access for CI, especially knowing that other CI's which are proven to work on forks can handle that.

However, it could be related to those checks

https://git.sr.ht/~sircmpwn/dispatch.sr.ht/tree/master/dispatchsrht/tasks/github/github_pr_to_build.py#L141 https://git.sr.ht/~sircmpwn/dispatch.sr.ht/tree/master/dispatchsrht/tasks/github/github_commit_to_build.py#L101

which has not fork. So testing a removal of it could be interesting.

Permissions on github should be less scary now and similar to the one travis has.