Thank you for the reply, looking forward to your next update post.
Honestly, I think it's perfectly fine to post those quarterly, I
wouldn't stress too much about it. Perhaps you could fill in the months
without pots with more brief bullet points on what is going on, even if
just on a mailing list, just like what you did here.

Cheers!

Hey Drew,

Sorry to hijack this thread, but in the meanwhile could you shed some
light on what's going on? Even just a couple of bullet points would go a
long way while we wait for the full post, in my opinion.

Thank you for the work :D

Cheers,

~tmpod

This release is *huuuge*!

Good job to everyone involved, and thank you so much for the quality
work <3

Cheers!

PS: Sorry for the lack of wrapping!
Wrote that on K-9 and forgot it doesn't hardwrap .-.

Hello!

Whenever I'm doing my periodic inbox sorting or when I'm trying to find a message in my archive, something that always bugs me is that aerc's search only looks for matches in titles, making it fairly difficult to quickly identify e-mails from a specific sender. 
I know I could (and probably should) use a more advanced and featureful tool for this (have yet to get my hands into stuff like notmuch), but it would certainly be cool to have it built in aerc. 

Is it already possible to do this? If not, would you be open to a patch implementing it?

Cheers!

~tmpod

SOCKS is a proxy protocol, and socksify redirects all internet traffic from a program to the specified proxy server (passed as an env var, for example).
In this case, the HTML filter is redirecting all potential requests to localhost, which most likely will fail, thus preventing any phoning home from e-mails.
So, to make your lynx filter, you should keep the socksify wrapper and only change the w3m call.

I hope this helps! :)

Applied, thank you!

Quickly amended the commit to reflow the paragraphs, and save a
roundtrip :P

To git@git.sr.ht:~tmpod/eigen
   ..  master -> master

Applied and pushed, thank you! :3

I made a small commit after yours just to reflow the paragraphs to the
100 char limit (which wasn't specfied anywhere, my bad!).


To git@git.sr.ht:~tmpod/eigen
   ..  master -> master

Lovely!

> I've managed to build Eigen and run it successfully with a bit of
> setup with KWallet. I've found that KWallet used with Eigen requires
> libqca-ossl which is a plugin to QCA, a Qt library that KWallet uses.

I hadn't noticed that, the plugin seems to have come already bundled
with my system's QCA package. Nice find!


> Detail how to build Eigen with cargo and how to run the program.
> Outline the dependencies needed to run it and the the issues one
> might run into when using Eigen without a keyring, or using KWallet
> without libqca-ossl. This will guide future users away from making
> the mistakes I did.