>I'm not sure how the text you include below is insulting.  It
>was meant in truth.  If you are unable to read my HTML posting,
>rendered in HTML, I felt you would be deprived, as it was well
formatted
>and I spent a large block of time over 3 days composing it.

You seem to be mistaking "unable" vs *unwilling*...

I was absolutely *able* to see your initial email, but the
blinding-white background made me feel around for the <del> key and kill
it unread.

In addition, you seem to be insisting on top-posting, despite being
mentioned to death that this is *not* a top-posting list, and that some
(quite many, actually) people object to it.  That says quite a bit about
you that you still insist on doing this despite others' preferences that
you and others *not* do so.


>I DID, despite the comments of those ignorant of email structure,
>post it in plaintext as well as in HTML.

And yet I still was temporarily blinded by a dazzling white background,
just so you could show off your cutesy colorful tables and all.


>I  *felt*  that those who read the plain text version were deprived.
>(Using the hyperbole of them being in a electronic 3rd world
>that only has tty terminals to display text, instead of monitors
>that can display proportional fonts).

Hey, if you want to display html content with all the associated markup
(tables, colors, various font-sizes/-faces, indentation, etc.),
absolutely go ahead and do so --- *ON A WEBPAGE*.

Text is for email, markup is for the web.

By repeatedly flouting the rules or even just conventions of a mailing
list, you're almost guaranteeing that you'll get shitcanned by quite a
few of the regulars who *really* don't want to put up with your or
anyone else's "bad manners".  We're civilised enough to not start flame
wars here over it, but we *will* eventually ignore you as if you don't
even exist.


>How is it that, "my" feeling, that someone who is reading "my" email,
>only in plaintext, when I put such effort into the HTML formatting, is
>insulting?

>The plaintext version comes *first* in the email.  Those who read the
>email in HTML, CHOSE, to do so.    How is that *my* fault?

"My, my, my. Me, me, me.  To Hell with everyone else, look at *my*
beautiful cutesy html email!!!"

Hey, I said it all before about this particular attitude, so I won't
repeat it.


>How was it decided that the list policy would ignore or not allow for
>RFC standard email?

Just because it *can* be done doesn't mean that it *should* be done.
The first hordes of AOL LOLcats started embedding graphics into email
and turning what should be a f'n *webpage* into mass-mailed emails.  I
don't really care about your last sightseeing trip or to look at 30
pictures of your kids/grandkids, so sending me such an email even once
is to get you *instantly* shitcanned.  I've done so, and explained why,
usually months after the fact when ostensibly after a bunch of emails
sent to me went unanswered, and I was asked "Why don't you reply to my
emails?".  "Hey, I didn't want to waste time DLing huge emails of
nothing but pictures, so I killfiled you..."


>Perhaps that decision needs to be re-examined?

I would prefer not to.

What you call "beautiful fonts", *I* call garish multicolored email that
just hurts my eyes.  The same argument you're making now, "I spent so
many hours formatting it beautifully so that you can all admire my
handiwork!" is the same argument to be made later when some ass-hat
*does* decide to send .swf files, videos, M$Word files, .pdfs, whatever.
No, nuh-uh, not gonna happen.


>And -no-, I'm not saying you open the door to flash-enabled players or
>embedded music, or animations.  Well, I could see embedding a video
>of how a user wants a Vim feature to work or even a 'howto use VIM',

See?  *RIGHT NOW* you opened that door just a crack, and look at the
cockaroaches swarming their way in.  "No I'm not saying to... but now
that you mention it, it *can* be a good idea..."

Put it on a webpage, post the url, and let whoever's interested take a
look, instead of *forcing* it on everyone.  Those of us who *choose* not
to can then simply skip it.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to