"Mutt has two main advantages: efficiency and configurability. It appeals to those who spend hours tuning their .vimrc files ... and who demand that their programs start up and respond instantly."
"Mutt has two main advantages: efficiency and configurability. It appeals to those who spend hours tuning their .vimrc files ... and who demand that their programs start up and respond instantly."
That search syntax looks nice: It almost makes me want to give mutt a try again but the thing about HTML not being supported gives me pause. For anyone that uses mutt (or other command line email...
That search syntax looks nice:
~fboss~d<2d~smeeting
searches for emails from boss, less than two days old, about meetings, placing the cursor on the first message found.
It almost makes me want to give mutt a try again but the thing about HTML not being supported gives me pause. For anyone that uses mutt (or other command line email clients):
How much HTML email do you receive and how do you deal with it?
The article touches on how to view HTML email (using lynx or a browser), but how does replying to such messages work?
Yeah, after some digging it sounds like you can also write emails in markdown and convert to html using pandoc, or just edit directly in html, tags and all. I probably won't go down that path...
Yeah, after some digging it sounds like you can also write emails in markdown and convert to html using pandoc, or just edit directly in html, tags and all.
I probably won't go down that path since I think it's important to use the same (or at least similar) tooling as my colleagues when I'm communicating with them. But when I get a chance I'll probably look into using mutt for ad-hoc bulk processing, e.g. cleaning up my inbox when it's nearly full or when things go sideways and our monitoring system starts spewing out a bunch of alerts.
I use Thunderbird, but I set it to view all incoming email in plaintext. Been doing this for years, without major difficulty. Once in an extremely rare while (once every 3 months maybe?) I might...
I use Thunderbird, but I set it to view all incoming email in plaintext. Been doing this for years, without major difficulty. Once in an extremely rare while (once every 3 months maybe?) I might have an email that I want ("need") to "view as Simple HTML".
Do you really receive email that is so broken that its plaintext version is incomprehensible?
I never said anything like that and I have no interest in the plaintext vs. HTML email debate that seems so prevalent in certain other corners of the internet.
Do you really receive email that is so broken that its plaintext version is incomprehensible?
I never said anything like that and I have no interest in the plaintext vs. HTML email debate that seems so prevalent in certain other corners of the internet.
"Mutt has two main advantages: efficiency and configurability. It appeals to those who spend hours tuning their .vimrc files ... and who demand that their programs start up and respond instantly."
That search syntax looks nice:
It almost makes me want to give mutt a try again but the thing about HTML not being supported gives me pause. For anyone that uses mutt (or other command line email clients):
How much HTML email do you receive and how do you deal with it?
The article touches on how to view HTML email (using lynx or a browser), but how does replying to such messages work?
Your reply will be in plaintext which all email clients can display, so it should work fine.
Yeah, after some digging it sounds like you can also write emails in markdown and convert to html using pandoc, or just edit directly in html, tags and all.
I probably won't go down that path since I think it's important to use the same (or at least similar) tooling as my colleagues when I'm communicating with them. But when I get a chance I'll probably look into using mutt for ad-hoc bulk processing, e.g. cleaning up my inbox when it's nearly full or when things go sideways and our monitoring system starts spewing out a bunch of alerts.
Yeah, mutt (and its forks) is pretty cool to script, which makes lots of operations pretty easy to customize.
I use Thunderbird, but I set it to view all incoming email in plaintext. Been doing this for years, without major difficulty. Once in an extremely rare while (once every 3 months maybe?) I might have an email that I want ("need") to "view as Simple HTML".
Do you really receive email that is so broken that its plaintext version is incomprehensible?
I never said anything like that and I have no interest in the plaintext vs. HTML email debate that seems so prevalent in certain other corners of the internet.
Sorry, I misunderstood.
For anyone who wants an alternative, there is aerc