N
Nikolai Weibull
OK. A lot of the time you will see new threads being spawned off old
ones on this list. This is very annoying if you have a mailer (mutt)
that supports threading of messages. Can you (the poster) please take
the time to simply type in (or better yet, use an alias)
(e-mail address removed) in the To: field of your mail, instead of
randomly picking a mail you have received from the list and press reply
(or however your mailer triggers this function). It is very annoying
when you're in a thread about common constructor idioms three levels
deep, and all of a sudden you find yourself reading about some problem
with ruby on a Windows system. I don't care about Windows! I care
about common constructor idioms. And it doesn't help that yet another
level is added by the author noting that the problem can be reproduced
in both versions 1.6.8 and 1.8.0 - and including the whole previous
posting, written by himself, in the one-line follow-up. The follow-up
also uses the oh-so-stupid --- Original Message --- thing that
Microsuck Outlook so non-standardly uses instead of proper mail quoting
so you can't immediately tell what's going on in the thread. So,
please, if you are going to post about something not related to any
previous thread, create a new one (so I can delete and ignore it if I am
so inclined). Thank you,
nikolai
P.S.
This mail is not targetted at a specific individual or group, just the
lists readers and writers in general. No harm was intended when posting
it.
D.S.
ones on this list. This is very annoying if you have a mailer (mutt)
that supports threading of messages. Can you (the poster) please take
the time to simply type in (or better yet, use an alias)
(e-mail address removed) in the To: field of your mail, instead of
randomly picking a mail you have received from the list and press reply
(or however your mailer triggers this function). It is very annoying
when you're in a thread about common constructor idioms three levels
deep, and all of a sudden you find yourself reading about some problem
with ruby on a Windows system. I don't care about Windows! I care
about common constructor idioms. And it doesn't help that yet another
level is added by the author noting that the problem can be reproduced
in both versions 1.6.8 and 1.8.0 - and including the whole previous
posting, written by himself, in the one-line follow-up. The follow-up
also uses the oh-so-stupid --- Original Message --- thing that
Microsuck Outlook so non-standardly uses instead of proper mail quoting
so you can't immediately tell what's going on in the thread. So,
please, if you are going to post about something not related to any
previous thread, create a new one (so I can delete and ignore it if I am
so inclined). Thank you,
nikolai
P.S.
This mail is not targetted at a specific individual or group, just the
lists readers and writers in general. No harm was intended when posting
it.
D.S.