4 ms·
The work involved in an effective inline reply is to snip out the irrelevant quote yet still leave enough context for what you were replying to. An inline repl
by hzhou321 7y ago
The work involved in an effective inline reply is to snip out the irrelevant quote yet still leave enough context for what you were replying to.
An inline reply with a large amount of irrelevant quotes so that people have to hunt down your reply is bad.
An email client that does not keep a thread and people can't effectively trace back old posts to recall context is bad.
A default rich text preference is bad. Email client can easily apply some heuristics or honoring something mark-down-like, but the base need be always in plain text.
- tatersolid 7y ago> A default rich text preference is bad. Email client can easily apply some heuristics or honoring something mark-down-like, but the base need be always in plain text. I’m a grey beard, using email since the early 1990s. All these years later, I’ve realized HTML email is better in every way than plain-text email. Basically, you get every “feature” of plain-text plus important semantic additions like hierarchical lists, <strong>, <em>, <h#>, <figure>, <blockquote> etc. that improve clarity of communication drastically. HTML email can and should be about much more than fonts and colors. A forum like LKML is basically useless without these, but they insist on old-Skool plain text which makes readability suffer greatly.