Live data from Hacker News

Aerc – An email client that runs in the terminal

aerc-mail.org

141–150 of 271 posts

Re: Aerc – An email client that runs in the terminal

#141

Earlier quoted context omitted.

I use a systemd timer to handle periodic calls to offlineimap, and that works really well compared to a corn-based work flow.

systemd timers are a cron-based workflow. A cron-based workflow is when you periodically check for work to do rather than get notified that there's work to do.

Yes that's true that they periodically check for work to do, but cron is not smart enough to know whether a service is already running - a systemd-timer can base it's timer from the point when a service completes. I think cron just fires up a service unless you build in some logic to check if it's running

Re: Aerc – An email client that runs in the terminal

#143
Great work! I'm looking forward to using it full time. A couple of quick comments.

1. It doesn't seem to work with when $TERM is set to some non-default setting. (panic: terminal entry not found) 2. When term is forced to xterm-256-color, aerc crashes when the window is resized.

Re: Aerc – An email client that runs in the terminal

#144

Earlier quoted context omitted.

Checkout offlineimap. Mutt can then use the synched directory from offlineimap.

offlineimap is cron-driven though, so it doesn't fetch mail "as soon as it arrives". I don't know that any offline-sync daemons uses IDLE though. isync / mbsync doesn't seem to either.

I wrote my own IMAP IDLE watcher (https://github.com/rakoo/). It only watches for IDLE events, all the actual mail retrieval is done by offlineimap. It's simplistic but it does (did) the job.

Re: Aerc – An email client that runs in the terminal

#147
post #124

Earlier quoted context omitted.

There's a ticket planned for adding a notmuch backend straight up: https://todo.sr.ht/~sircmpwn/aerc2/105 No indirection through mbsync & maildir. This shouldn't be terribly hard - if you're interested in working on this feature, swing by the IRC channel to get a rundown of the technical details. There's also a ticket for search in general: https://todo.sr.ht/~sircmpwn/aerc2/93 Which will probably be implemented for…

i am looking forward to this. i am currently using supmua, the ancestor of notmuch, and i haven't been able to switch to any other notmuch based terminal client because their interfaces all felt inferior to sup. aerc is the first client i see that does the interface with multiple switchable screens right from the start. notmuch integration with the ability to keep virtual folders based on tags and on searches is the…

You should have a look at astroid (https://github.com/astroidmail/astroid). It is written by one of the ex-maintainers of sup but uses notmuch, so the workflows are mostly similar. It's not in a terminal though.

Re: Aerc – An email client that runs in the terminal

#148

Earlier quoted context omitted.

>A daemon that pulls new mail from my IMAP servers to my local maildir as soon as it arrives. (I know mutt has an IMAP mode, and it looks like that's aerc's primary mode of operation, too, but I like to have a local copy of my entire mail archive.) What's wrong with fetchmail? Granted, it's not "as soon as it arrives", but you can run it every minute if you want.

These days, a lot of services with 2FA type emails or validation emails expect you to receive them within seconds. Also, how many times have you spoken to someone on the phone for them to say "I've just sent you the details.... can you see it yet?"

> These days, a lot of services with 2FA type emails or validation emails expect you to receive them within seconds.

Within seconds, really? I haven't encountered a single service like that.

> Also, how many times have you spoken to someone on the phone for them to say "I've just sent you the details.... can you see it yet?"

True but there's an easy solution: Fire up a terminal or even use a keyboard shortcut to run offlineimap manually within a split second.

Re: Aerc – An email client that runs in the terminal

#149
post #89

I haven't dug too deep into the features or how this works yet, but it's very exciting to see any kind of movement in this space at all. I've spent a lot of time configuring mutt just the way I like it, but I'd throw it all away in a heartbeat for a good, modern alternative. My wishlist: * A daemon that pulls new mail from my IMAP servers to my local maildir as soon as it arrives. (I know mutt has an IMAP mode, and i…

>80-char lines are too short for desktop displays

Nothing makes them "too short for desktop displays". Text is not supposed to fill all/most of the available display width:

“Anything from 45 to 75 characters is widely regarded as a satisfactory length of line for a single-column page set in a serifed text face in a text size. The 66-character line(counting both letters and spaces) is widely regarded as ideal.” -- The Elements of Typographic Style Applied to the Web

Re: Aerc – An email client that runs in the terminal

#150
post #94

Earlier quoted context omitted.

> 80-char lines are too short for desktop displays and too long for small phones (leading to awful linebreaks), which makes me the guy whose emails never look right. RFC 3676 [1] describes the format MIME parameter for text/plain content type documents which solves this issue. Unfortunately, it does not work well when sending inline patches via email since it introduces trailing whitespace. [1] https://www.ietf.org/r…

format=flowed has many other problems, aside from mangling mails. It gets lost easily; intermixing mail clients that handle it with those that don't (or have been intentionally configured to ignore it because it mangles mails) produces poor results; it often breaks signatures; it makes it harder to quote and reply to emails; in general, it means the person on the other end will not see exactly what you sent.

Thus the nickname: format=flawed
Post reply on HN