~labrat

Recent activity

Re: [PATCH v2] propagate error from sendmail 14 hours ago

From Reto to ~sircmpwn/aerc

Merged to master, thanks!

Cheers,
Reto

Re: Error message when replying with quote a day ago

From Reto to ~sircmpwn/aerc

Ah, update to master that should fix your issue.

That's a bug in the released version

Re: Error message when replying with quote a day ago

From Reto to ~sircmpwn/aerc

because aerc can't read the message part...
usually due to some structural error or a bug in the decoding.

Re: UX Help a day ago

From Reto to ~sircmpwn/aerc

:recall should do the trick

Re: Pinning repositories a day ago

From Reto to ~sircmpwn/aerc

Not quite sure if the aerc list cares much about sr.ht issues ;)

Please resend to the proper list.

Re: notmuch: Unknown backend notmuch 2 days ago

From Reto to ~sircmpwn/aerc

On 20 September 2020 17:31:43 CEST, Tyler Childs <email@tychi.me> wrote:
>From your guidance, installing libnotmuch-d
>In my config, I've got `notmuch://~/.mail/.notmuch`. Any tips for this
>one?

source = notmuch://~/.mail

The .notmuch folder is implied and must not be specified.

Re: notmuch: Unknown backend notmuch 2 days ago

From Reto to ~sircmpwn/aerc

On 19 September 2020 19:35:07 CEST, Tyler Childs >however when I run aerc, I get the error "Unknown
>backend notmuch".

Yes, you didn't compile it in.

>When I originally ran make, I forgot the flag, but tried again with
>`GOFLAGS=-tags=/usr/bin/notmuch make -B` and I'm assuming that worked.

No, that's not how this works... that's not how any of this works.

Don't deviate from the instructions in the readme.
`GOFLAGS=-tags=notmuch make`

You need the notmuch header file (notmuch.h) in the usual library path and a working c compiler.

Re: [PATCH] doc: fix typo in aerc man page 5 days ago

From Reto to ~sircmpwn/aerc

Merged, thanks.

Greetings,
Reto

Re: maildir: add recent handling 7 days ago

From Reto to ~sircmpwn/aerc

On Mon, Sep 14, 2020 at 11:08:58PM +0200, Galen Abell wrote:
> The new patches don't seem to work quite right though; it looks like
> when I get a new message it very briefly flashes the recent count and
> then immediately clears it.

Yup, working as designed actually. Not that I say that this is how we should be
doing it...

>I'm also not sure if we want the recent
> trigger to fire when aerc starts up and handles new messages, since it
> seems like it should only happen when aerc is running in the background.
> That might require some more refactoring though so not a priority.

That's nice in principle, however what's "in the background" is a very hard question

Re: maildir: add recent handling 8 days ago

From Reto Brunner to ~sircmpwn/aerc

Hm, on a second thought...
When do we actually want to clear the recent flag?
I mean we could do it when switch folders / read the message instead of automatically.

What is the proper use here?

Not sure how many people actually understand the recent flag and how it differs
from the seen flag...
So not auto clearing it might confuse the one or other user.

Opinions?