From: Jack <ostroffjh@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Posting etiquette: Was: Getting error message when launching X-Window apps in Cygwin
Date: Sat, 09 Feb 2019 16:34:00 -0000 [thread overview]
Message-ID: <c78b2a1d-9cb9-42db-46cf-6af63b8e4f6e@users.sourceforge.net> (raw)
In-Reply-To: <5C5EE7D2.2010404@tlinx.org>
On 2/9/19 9:46 AM, L A Walsh wrote:
> If a list is a conversational list where people think everyone
> reads everything, then maybe chronological might be better, but
> even many forums will show you the newer messages first.
The behavior/display of a list of messages does not have to be the same
as the behavior within each message.
> Does that help or make sense, or should I have read through the next
> 700 messages to see if you found a solution to you situation.
While I don't know of any forum that does threading, most email programs
do, so replies to a request for help SHOULD be listed directly below it
in most email programs. (certainly true in (most of) the ones I use.)
> But it could be very confusing if people always started at the
> beginning of their email and read downwards.
Another part of the etiquette of bottom posting lists is to trim what
you quote down to what you are answering/replying to. [Normally I would
use ... or "snip" but here I think I've kept enough for context.]Â What
"I" find really annoying is those lists where people with post a reply,
without quoting ANY of the original question - so you get messages like
"Click the third link on that page." with no context. That's possibly
OK if you see it displayed right under the first message, but quite
meaningless otherwise. I agree that I don't want to scroll through
pages of previously read stuff to see the new content, but if it's not
relevant to the "current" message, why not trim it out?
You can manage long discussions by either having the entire history in
one file/message, or by keeping the entire list of messages and keeping
each message short and to the current point. In the first case, it may
be easier to top-post new content, but then you have no reason to keep
old messages, as long as nothing does get trimmed. I think difficulties
arise when mixing the two approaches, which is probably inevitable with
email lists which get archived and even more so for cases like usenet,
where you can either post or email.
I generally consider it as "local custom."Â Some lists/forums want one,
some want the other. As long as it's made clear, why not follow the
requested style? (Another way to look at is as religion, which suggests
there is little point trying to change people's minds.)
Jack
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-02-09 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308285295.576965.1549657291745.ref@mail.yahoo.com>
2019-02-08 20:21 ` akshay chavan via cygwin
2019-02-09 6:27 ` akshay chavan via cygwin
2019-02-09 13:50 ` Andrey Repin
2019-02-09 14:46 ` L A Walsh
2019-02-09 16:34 ` Jack [this message]
2019-02-09 18:26 ` Posting Order (was: Getting error message...) Brian Inglis
2019-02-09 23:02 ` bzs
2019-02-10 0:36 ` Posting Order L A Walsh
2019-02-10 0:36 ` L A Walsh
2019-02-10 6:13 ` Brian Inglis
2019-02-09 19:06 ` Getting error message when launching X-Window apps in Cygwin Vince Rice
2019-02-10 0:02 ` L A Walsh
2019-02-10 0:43 ` Vince Rice
2019-02-10 8:43 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c78b2a1d-9cb9-42db-46cf-6af63b8e4f6e@users.sourceforge.net \
--to=ostroffjh@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).