If anyone wants to see an example of why thread hijacking is
bad, have a look at the archive:

http://groups.google.com/group/vim_use/topics?start=70

The above currently shows topic "is the [Esc] key not very
unreachable?" as the first message on Jun 1 (if you read my
message after some time, you might need to click "Older" to go
back to Jun 1).

If I am interested in controlling the cursor, I am not going to
look in the above thread. But, clicking the thread goes to:

http://groups.google.com/group/vim_use/browse_thread/thread/fe5171e6047b089f

which shows 26 messages. Towards the bottom, we see that the
subject has changed to "Hide cursor" and a totally unrelated
conversation starts (nothing to do with Esc).

By the way, the thread also illustrates why a simple signature
is much better than a bunch of rubbish.

My humble opinion is that we should NOT bother changing the
subject or thread when replies start wandering down some path
that is not wholly related to the thread. Life is too short to
optimise stuff like that.

However, NEW QUESTIONS should be NEW MESSAGES. Again, I'm not
going to repost someone's question for them because I'm too
grumpy, but also because we would have me reposting someone's
message and replying, while you repost it and reply in another
thread, while someone else just replies to the question, so we
would have three threads.

I would be very happy if someone is the first person to reply,
and they would like to politely NOT answer the question but say,
"please create a new message and ask your question again, see
link following".

Our friendly guide includes the following:

http://groups.google.com/group/vim_use/web/vim-information

    If you have a new question, create a new message
    (do not reply to a message with a new question
    because all replies are kept in one thread).

John


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

Reply via email to