I have been using it for the last weeks. It’s nice, although I didn’t have good luck with the documentation. I think some of the examples and capabilities are lacking, and the procedure for reporting/asking something seemed really convoluted with respect to something more plain like GitHub. Furthermore, another problem that I have is that sometimes I lose connection to the mail servers, and it’s imposible to recover it without closing and reopening the app. I am missing something like reconnect/refresh.
Aerc – a pretty good (terminal) email client
21–30 of 51 posts
Re: Aerc – a pretty good (terminal) email client
#22I have been using it for the last weeks. It’s nice, although I didn’t have good luck with the documentation. I think some of the examples and capabilities are lacking, and the procedure for reporting/asking something seemed really convoluted with respect to something more plain like GitHub. Furthermore, another problem that I have is that sometimes I lose connection to the mail servers, and it’s imposible to recover…
> Asynchronous IMAP support ensures the UI never gets locked up by a flaky network, as mutt often does
Seems to have been made with flaky connections in mind, would be weird if there wasn't a way to recover.
But on that note, isn't it local/offline-first? The first feature that comes in mind for a email client is "download all mail to store locally so I can browse/search them anytime", is that not how this client works?
Re: Aerc – a pretty good (terminal) email client
#23Earlier quoted context omitted.
Also sway, but hacker news doesn't always hold him in that high of an opinion, probably mostly of his Rust criticisms... But I use many of his tools, all top notch!
He has over 25k karma on here. The data doesn't fit your assertion.
I'm not worthy of high opinion yet I also have ~25k karma. Karma matters less than you think.
Re: Aerc – a pretty good (terminal) email client
#24I have been using it for the last weeks. It’s nice, although I didn’t have good luck with the documentation. I think some of the examples and capabilities are lacking, and the procedure for reporting/asking something seemed really convoluted with respect to something more plain like GitHub. Furthermore, another problem that I have is that sometimes I lose connection to the mail servers, and it’s imposible to recover…
> Asynchronous IMAP support ensures the UI never gets locked up by a flaky network, as mutt often does Seems to have been made with flaky connections in mind, would be weird if there wasn't a way to recover. But on that note, isn't it local/offline-first? The first feature that comes in mind for a email client is "download all mail to store locally so I can browse/search them anytime", is that not how this client wor…
No, it does not store emails offline by default (though you can configure it to use maildir and use isync to pull emails down, this is what I do in my configuration). In my opinion this is the major design mis-step of aerc which will be corrected by a future mail client.
Re: Aerc – a pretty good (terminal) email client
#25I swapped over to aerc from mu4e, it’s very pleasant to use. I would easily recommend it.
Why this over regular client ?
I use mutt but will give this a try.
But another perspective on why use a cli over a regular client. Though there's a bit of a vogue for terminal apps in dev circles, I don't favour them in general. I like GUIs. I want my computer to use 21st century tech for UIs.
But unfortunately (on Linux at least) all the GUI IMAP clients I've tried are terrible. Not because they are GUIs but because they're all either buggy or have awful 1990s corporate interface design or lack even essential keyboard shortcuts, or are just infeasably slow.
So mutt it is, which at least seems to be well-crafted, is quick, and can be configured to be pretty usable. I'd replace it with an excellent GUI app if there were such a thing.
Re: Aerc – a pretty good (terminal) email client
#26I have been using it for the last weeks. It’s nice, although I didn’t have good luck with the documentation. I think some of the examples and capabilities are lacking, and the procedure for reporting/asking something seemed really convoluted with respect to something more plain like GitHub. Furthermore, another problem that I have is that sometimes I lose connection to the mail servers, and it’s imposible to recover…
> Asynchronous IMAP support ensures the UI never gets locked up by a flaky network, as mutt often does Seems to have been made with flaky connections in mind, would be weird if there wasn't a way to recover. But on that note, isn't it local/offline-first? The first feature that comes in mind for a email client is "download all mail to store locally so I can browse/search them anytime", is that not how this client wor…
It has improved lately but no, it does not handle flaky connections well. And it is online by default.
Re: Aerc – a pretty good (terminal) email client
#27I use an email client called bower, which is fairly light on features, but has one killer feature: it works with remote notmuch databases.
So I get great search, but can easily open attachments locally, or even compose in a GUI editor.
Re: Aerc – a pretty good (terminal) email client
#28how would I use aerc and not maintain a go toolchain?
Re: Aerc – a pretty good (terminal) email client
#29I love it, answers the question. “What would vim be like as a web client” I use it regularly.
Re: Aerc – a pretty good (terminal) email client
#30how would I use aerc and not maintain a go toolchain?
Install it from your local package manager: