> start each email with a statement like "I'm sorry for top-posting, I > know this is not usual list procedure, but I can't configure my XXX > device to bottom post" and a later responder can trim as needed.
Heh, does "XXX" stand for profanity, or a make/model of device? ;-) I too am more lenient when it comes to device limitations (no less irksome as a recipient, though at least more understandable) but I do agree with Ben's points: > The final suggestion might be a bit controversial, but it does have > some advantages: > > 1. It alerts us that the poster is trying to respect our policies, is > unable to, but still wants to make a meaningful contribution > 2. It alerts readers of the thread that we DO have policies, and they > should follow them if possible > 3. It does not drive away contributors for reasons (somewhat) beyond > their control. > > I think making exceptions in rare cases like Derek's will help with > the "polite" vs. "informative" balance. It seems to boil down to a "my time as a querier is more valuable than your time as a respondent/answerer" attitude. The more civil/respectful the querier is (in both text-content and in formatting), the more likely they'll get an answer. Top-posting _can_ be done respectfully as Ben suggests, but the more adherent to list guidelines, the more respectful it is, and thus more likely the major players on the list will care. I don't remember any grievous disrespect from Derek in the thread (I'd have to reach into my killfile to find the handful of folks I've had to plonk on this list...most have unsubscribed to the best of my knowledge. The comp.lang.python list is the second best list I'm on in terms of [signal/civility]-to-noise, and my killfile from that is far longer) -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
