Mail Archives: djgpp/2004/07/23/23:28:16
I'm continuing this off-topic conversation because it's interesting,
and marginally relevent to the djgpp forum, but let's not let it drag
on too long as it's not that important here. I'm saying this because
I needed an example of a time where top-posting makes sense ;-)
> Yes. But then there is honest opinion that you should NOT top post if
> you know what you're doing, which I don't mind telling people.
If you know what you're doing, you don't need the advice - the text
goes where it makes sense in the conversation (like my first
paragraph). My rule of thumb is to put replies immediately after what
I'm replying to, when it's a direct reply like that. Unrelated text
in the same message would go on top, as if I said that in person
before getting to the replies.
The problem with bottom posting happens when you don't trim the quoted
text enough. Blind readers are forced to wait through the untrimmed
text before they hear the reply. They end up listening to the same
quoted text over and over again as they go through the messages.
> Ok. But now it looks like I've managed to get "> " (two spaces).
I think the '>' is more important than the spaces following it, but
might as well fiddle with it now while you're thinking about it (your
second message looked right). You can use the djgpp mail archives to
see your message from the "other side" if needed (but please don't use
the djgpp forum to test your software; use one of the *.test groups
like alt.test for that).
- Raw text -