Skip to content

Instantly share code, notes, and snippets.

@mccutchen
Created November 30, 2010 20:59
Show Gist options
  • Save mccutchen/722389 to your computer and use it in GitHub Desktop.
Save mccutchen/722389 to your computer and use it in GitHub Desktop.
Plain text vs. HTML emails
Wilbur -
It's 2010 now. People are twatting left and right. We have telephones that
can plot traffic in real time. So HTML email, while not thematically true to
the to it's DARPANET precursor, is now the defacto standard. I don't plan to
be quitting it any more than I'm planning on cutting off my fingers with a
butcher knife.
W
*If I'm not misremembering what you told me in the past, you prefer
plaintext because it doesn't make computer code illegible. I in turn wonder
why you don't have a separate email account for that purpose?
On Tue, Nov 30, 2010 at 11:25 AM, Will McCutchen <[email protected]>wrote:
> > And then after sending I remembered your Ludditious clinging to plaintext
> > email. So all the embedded links I suppose will be omitted...
>
> Unfortunately, Gmail does not allow me to set a preference for always
> viewing the plaintext version of a received email, so I always see the
> stupid "rich" text version, links (and sometimes crazy background
> images, etc.) and all. So I always receive your embedded links.
>
> It does, however allow me to control whether I send out plaintext
> emails by default, which I almost always do. Which means it's a pain
> in the ass for me to forward your inline-link-ridden emails to other
> people, because the links are lost in the conversion to plaintext.
>
> Basically, quit it!
Wilbur -<div><br></div><div>It&#39;s 2010 now. People are twatting left and=
right. We have telephones that can plot traffic in real time. So HTML emai=
l, while not thematically true to the to it&#39;s DARPANET precursor, is no=
w the defacto standard. I don&#39;t plan to be quitting it any more than I&=
#39;m planning on cutting off my fingers with a butcher knife.</div>
<div><br></div><div>W</div><div><br></div><div>*If I&#39;m not misrememberi=
ng what you told me in the past, you prefer plaintext because it doesn&#39;=
t make computer code illegible. I in turn wonder why you don&#39;t have a s=
eparate email account for that purpose?</div>
<div><br><div class=3D"gmail_quote">On Tue, Nov 30, 2010 at 11:25 AM, Will =
McCutchen <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">mccu=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">&gt; And then after sending I remembered your Ludditious =
clinging to plaintext<br>
&gt; email. So all the embedded links I suppose will be omitted...<br>
<br>
</div>Unfortunately, Gmail does not allow me to set a preference for always=
<br>
viewing the plaintext version of a received email, so I always see the<br>
stupid &quot;rich&quot; text version, links (and sometimes crazy background=
<br>
images, etc.) and all. =A0So I always receive your embedded links.<br>
<br>
It does, however allow me to control whether I send out plaintext<br>
emails by default, which I almost always do. =A0Which means it&#39;s a pain=
<br>
in the ass for me to forward your inline-link-ridden emails to other<br>
people, because the links are lost in the conversion to plaintext.<br>
<br>
Basically, quit it!<br>
</blockquote></div><br></div>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment