From: Kusoneko <kusoneko@kusoneko.moe>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Email clients
Date: Mon, 31 Jul 2023 13:32:06 -0400 (EDT) [thread overview]
Message-ID: <1eb06d73-13d4-4f6e-8de7-791afd547c0b@kusoneko.moe> (raw)
In-Reply-To: <9e07b48f50e29a4d260f88297f9f0d386075a97a.camel@connell.tech>
Jul 31, 2023 13:23:21 Matt Connell <matt@connell.tech>:
> On Mon, 2023-07-31 at 20:16 +0300, Alexe Stefan wrote:
>>> Normally I would be in the chorus of "why do I need a whole entire
>>> web
>>> engine for an email client" but I'm also in the group of people who
>>> knows full well what the answer is.
>>
>> What is the answer?
>> Mutt doesn't need a web engine.
>
> For the reason that you just demonstrated for the class: HTML emails.
>
> Now, your simple mail shows just fine in a plain text only mail client,
> but in my world, and I'd wager most people's world, handling HTML
> messages (which includes CSS for legibility) is a necessity to some
> varying degree.
>
> Don't get me wrong, I'm "team plaintext" all day every day but I'm not
> going to make my life more difficult on principles. There are hills
> worth dying on but this isn't mine.
Iirc, you can setup mutt to open html emails either in a web browser or with something like w3m. There's no need for a web engine in a mail client when you have a perfectly workable web engine in the browser. You can easily reply to html mail in plain text either way, and most html mail are marketing or newsletter emails from companies where replying isn't needed anyways.
next prev parent reply other threads:[~2023-07-31 17:32 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 0:29 [gentoo-user] Email clients Peter Humphrey
2023-07-29 0:38 ` Jack
2023-07-29 2:37 ` Bryan Gardiner
2023-07-29 8:52 ` Wols Lists
2023-07-29 10:13 ` Arsen Arsenović
2023-07-29 11:20 ` Wols Lists
2023-07-29 13:54 ` Arsen Arsenović
2023-07-29 14:21 ` Wols Lists
2023-07-29 14:50 ` Arsen Arsenović
2023-07-29 16:27 ` Wols Lists
2023-08-02 7:16 ` [gentoo-user] " Nuno Silva
2023-07-29 5:53 ` [gentoo-user] " Philip Webb
2023-07-30 12:07 ` Frank Steinmetzger
2023-07-30 12:25 ` Peter Humphrey
2023-07-29 6:56 ` Neil Bothwick
2023-07-29 11:01 ` Peter Humphrey
2023-07-29 11:23 ` Wols Lists
2023-07-30 19:02 ` Neil Bothwick
2023-07-30 22:53 ` Peter Humphrey
2023-07-30 23:11 ` Neil Bothwick
2023-07-31 7:34 ` Wols Lists
2023-07-31 12:33 ` Peter Humphrey
2023-07-31 13:26 ` Neil Bothwick
2023-07-31 16:03 ` Peter Humphrey
2023-07-31 16:25 ` Peter Humphrey
2023-07-31 17:26 ` Peter Humphrey
2023-07-31 18:13 ` Neil Bothwick
2023-07-31 18:17 ` Michael
2023-08-01 9:53 ` Peter Humphrey
2023-08-01 10:42 ` Michael
2023-08-01 16:56 ` Peter Humphrey
2023-07-31 17:57 ` Michael
2023-08-01 9:55 ` Peter Humphrey
2023-07-31 18:14 ` Neil Bothwick
2023-07-31 14:19 ` Wols Lists
2023-07-31 15:55 ` Peter Humphrey
2023-08-01 18:51 ` Wols Lists
2023-08-01 23:39 ` Peter Humphrey
2023-07-29 9:26 ` Michael
2023-07-31 1:12 ` Matt Connell
2023-07-31 16:14 ` Peter Humphrey
2023-07-31 16:59 ` Matt Connell
2023-07-31 17:16 ` Alexe Stefan
2023-07-31 17:23 ` Matt Connell
2023-07-31 17:32 ` Kusoneko [this message]
2023-07-31 17:52 ` [gentoo-user] " Grant Edwards
2023-07-31 18:46 ` Kusoneko
2023-07-31 18:57 ` Matt Connell
2023-07-31 20:22 ` Grant Edwards
2023-07-31 20:24 ` David Rosenbaum
2023-07-31 19:27 ` [gentoo-user] " Laurence Perkins
2023-07-31 17:36 ` Jack
2023-07-31 17:43 ` [gentoo-user] " Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1eb06d73-13d4-4f6e-8de7-791afd547c0b@kusoneko.moe \
--to=kusoneko@kusoneko.moe \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox