R
Richard Heathfield
Roose said:Thanks,
That's quite all right.
check out this one too:
"Don't get involved in flame wars. Neither post nor respond to incendiary
material."
I have not posted any incendiary material in this thread. If you think I
have breached this guideline, it can only be because you think that /your/
material is incendiary. If so, then you have breached the guideline
yourself. I, however, have not.
You're in no position to tell me not to top-post, clearly.
I have *asked* you not to top-post. There is a difference between asking and
telling.
And this is
not recognition of those rules as authority.
It appears from what you say that the only authority you recognise (and
expect us to recognise) is you.
I already said that I am perfectly capable of quoting, when I think it's
more clear. I top-post when that's more clear.
I disagree that putting the response before the stimulus is ever "more
clear".
<newsreader "ergonomics" point dealt with elsethread, so I've snipped it
here>
Just like HTML e-mail used to be an ungodly annoyance, it is coming into
acceptance because of greater disk space, bandwidth, and more e-mail
clients
support it. Oh times they change.
HTML e-mail remains an ungodly annoyance. Oh times they stay the same.
Apparently you don't really understand how Usenet works.
Well, you certainly don't, if you think you can make unsupported and indeed
patently false claims in this newsgroup without being challenged.
No shit. I never said that I owned the group. You're the ones telling ME
what to do.
I have /asked/ you to stop top-posting. If you wish to be taken seriously in
this newsgroup (and it appears that you don't), it would be wise to follow
the accepted conventions of the group.
I'm not telling you to do anything. I simply suggest that if
you're so keen on following netiquette, then killfile me already.
But what if you were to start dispensing language advice? If you were in
every regular contributor's killfile, who would correct your errors?