Saluton Charles :)

On Wed 10 Jun 2009 18:58 +0200, Charles Campbell <[email protected]> dixit:
> Teemu Likonen wrote:
>> Perhaps you could start by elaborating the semantics of hijacking in
>> this mailing list's context. What makes a change in the subject of
>> discussion (and Subject header) hijacking?

If the change in the subject is not meant to adapt the subject for a
"morphing" thread? Sometimes the themes in a conversation suffer a kind
of "evolution", and in fact is better to change the subject in that
case.

If you change the subject to start a new thread, you're "hijacking". Not
bad per se (except that replying when you intend to make a new thread is
a bad habit) but it breaks threading. You end up with two unrelated
conversations in the same thread when the intention was having two
threads.

>> But if vim-use list is seen only or mostly as a question-answer
>> mailing list, rather than a discussion list, then perhaps I can
>> understand that changing the subject of a question-answer thread may
>> feel like an unhelpful practice. Haven't seen such "changing the
>> subject means hijacking and is rude" view anywhere else, though.

I wouldn't say "rude", I would say "unwise", as Chip said.

> As Tim Chase implied, some folks may not even see the new topic on a
> hijacked thread, so it is unwise to hijack a thread from an
> originator's viewpoint (assuming s/he wants a wide audience).

Exactly. Myself, I didn't see Carsten post because I was not following
the thread where the subject was changed. This reason is enough, I
think, to avoid replying instead starting a new thread. Of course, the
one that is affected the most is the poster, who may not get any answer.

-- 
Raúl "DervishD" Núñez de Arenas Coronado
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

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

Reply via email to