Switching to the Mutt Email Client
11–20 of 246 posts
Re: Switching to the Mutt Email Client
#12Console based mail-clients are very powerful and fast to use. I was a long-time mutt user before I started writing my own mail client, with complete scripting provided by Lua. Having a real scripting language allows a lot of useful features, at times using mutt felt a little bit too constrained, although it has a lot of features and is very very flexible in its own right: https://github.com/lumail/lumail
The article seems to think that everyone should switch away from HTML. But how well does console clients deal with HTML emails. It's not like you can tell everyone to stop sending you HTML.
No, but HTML emails, 99% of them, are just plain text in an HTML markup. You won't miss garish colors or font choices.
As for embedded images etc, you can still view them with plain text mail clients (as attachments).
Re: Switching to the Mutt Email Client
#13Console based mail-clients are very powerful and fast to use. I was a long-time mutt user before I started writing my own mail client, with complete scripting provided by Lua. Having a real scripting language allows a lot of useful features, at times using mutt felt a little bit too constrained, although it has a lot of features and is very very flexible in its own right: https://github.com/lumail/lumail
The article seems to think that everyone should switch away from HTML. But how well does console clients deal with HTML emails. It's not like you can tell everyone to stop sending you HTML.
If I really end up having to read an HTML email those can be displayed "inline" using a text browser such as w3m. If the HTML is mostly text it works pretty well, for instance: https://svkt.org/~simias/mutt-html.png
If however it's image or css-heavy and doesn't work well in text-only form there's still the option to tell mutt to open the email in your web browser. Of course in this case there are security implications so it's probably best not to do it from untrusted sources.
Re: Switching to the Mutt Email Client
#14Interestingly, I went the other way. I used to have mutt for years, then went through a dark phase (macOS Mail.app, Evernote and Things) and finally concluded to Emacs with mu4e. Integrating mail with Emacs was the best idea ever, because Emails include either todos or serve as reference in projects. Creating todos from Mails as well as linking to them from org-mode is only a shortcut away. I have never had a more ea…
this is the only solution that i found to work for me. I know that i have to handle it now inside wunderlist. but it works ok for me because is better sorted.
i use evernote for some of the stuff, and i try to write everything. sure its not ideal but it is a lot better then it used to be where i would forget about some important stuff.
Re: Switching to the Mutt Email Client
#15In most big companies you can't really afford to do any email client shenanigans. You probably need to see HTML emails, handle calendar invites, etc.
Re: Switching to the Mutt Email Client
#16Very good. I could easily complement this with a calendar terminal app. Anyone knows of a terminal calendar app to keep appointments ? (similar to the apple calendar, or google calendar)
Re: Switching to the Mutt Email Client
#17Very good. I could easily complement this with a calendar terminal app. Anyone knows of a terminal calendar app to keep appointments ? (similar to the apple calendar, or google calendar)
Re: Switching to the Mutt Email Client
#18But, unfortunately, I had to go back to Thunderbird. With the exception of free software mailing lists, people simply do not know how to use email. Bottom quoting is the default. We can thank Microsoft for that one, I think. I can't understand why anyone thought it was a good idea to attach the previous message to the bottom. Most people just accept this as the way email is and never question how unbelievably stupid it is.
Then you've got all the HTML shit that people put in there. And the fact that many clients are simply broken and don't write the headers correctly which breaks threading. This is often confounded by broken servers which garble the headers a second time.
It's amazing that something as simple as mutt or gnus (emacs) has everything you need: threaded messaging and convenient composition. Inline quoting is surely the only sane way to do quoting. Why would you assume the person you reply to has deleted their own message? My message to you is right there in the same thread in my client. Don't send it back to me. But do make it clear which parts of it you are addressing (inline quoting). You had to laugh when Google reinvented threaded messaging in the 2000s and advertised it as some groundbreaking new thing.
So I gave up. I use a client that can deal with the stupid shit that other clients spit out. I also bottom quote now. Why? Because if you do inline quoting, MS Outhouse web client thinks that everything after the beginning of the quotation is a copy of the previous message and folds the whole thing, meaning your recipients get back what looks like an empty message. Really.
Re: Switching to the Mutt Email Client
#19I feel that the folks that do this aren't working for big companies. In most big companies you can't really afford to do any email client shenanigans. You probably need to see HTML emails, handle calendar invites, etc.
Re: Switching to the Mutt Email Client
#20I started using emacs for email back in my uni days. I used Dovecot to run an IMAP server locally which would get my mail when it could. This made it very quick in emacs because it wouldn't have to wait for any remote server. But, unfortunately, I had to go back to Thunderbird. With the exception of free software mailing lists, people simply do not know how to use email. Bottom quoting is the default. We can thank Mi…
Gah; that explains it. Occasionally I get a reply saying "you just sent me a blank email", while the text of my email is quoted right there in the email they've just sent me!