archive mirror
 help / color / mirror / Atom feed
From: CaT <>
To: Steven Cole <>,
	bill davidsen <>,, Tomas Szepe <>
Subject: Re: Posting format
Date: Fri, 25 Jul 2003 09:24:13 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Jul 24, 2003 at 11:47:32AM -0400, Robert L. Harris wrote:
*51 lines of unnecessary quoting snipped*
> > More exposition regarding top vs bottom posting: Replying at the bottom
> > results in an easily parseable tree. Consider the following conversation
> > where everyone replies at the bottom.
> On the other hand if everyone posted at the top it would be considerably
> easier reading for those who have been following the conversation
> without having to scroll down and figure out where comments and the
> conversation is at.  You could read just the top post and go from there.

That's why you snip your quoting appropriately.

> For those new to the conversation they can just start at the bottom and
> scroll up.  When the next post comes in they just read the top post

Or rather, scroll to somewhere near the bottom, scroll down some, scroll
up to the next message, scroll down some, scroll up, scroll down, etc.
All depends on how the replies were done. 

> again instead of scrolling down to the bottom or middle somewhere to
> figure out what/when/where.

People who know how to trim quoting appropriately make this a non-issue.
Generally the reply begins on the first visible page.

The other advantage is that going past the bits of relevant quoted text,
even just to quickly pass your eyes over them, gives you a nice reminder
of what is being replied to and makes the subject fresher in your mind.
It also helps clue you into what the sender is really replying to so that
there's (potentially) less misunderstanding.

> Using VI and Mutt, the cursor starts at the top not the bottom or
> anywhere in the middle so there's and ease of use for CLI mail readers
> as well instead of the GUI oriented.

I use mutt and vim. This is a non-point. The spacebar works. With vi
ndd works for quote removal (where n is the number of lines). For vim
you have shift-v to begin your selection and just move the cursor down
to where you want to cut. If the person you're replying to did their
job then you doing yours is simplicity in itself. If they don't then
it becomes more painful but it still is not difficult (or complex -
just takes a wee bit longer).

"How can I not love the Americans? They helped me with a flat tire the
other day," he said.

  parent reply	other threads:[~2003-07-24 23:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 20:18 2.6.0-test1-ac3 still broken on Adaptec I2O Robert L. Harris
2003-07-23 20:22 ` Christoph Hellwig
2003-07-23 22:00   ` Robert L. Harris
2003-07-23 22:53     ` Tomas Szepe
2003-07-23 23:32       ` Posting format bill davidsen
2003-07-24  0:52         ` Tomas Szepe
2003-07-24 15:14         ` Steven Cole
2003-07-24 15:47           ` Robert L. Harris
2003-07-24 16:03             ` Tomas Szepe
2003-07-24 16:52               ` Steven Cole
2003-07-24 17:15                 ` Robert L. Harris
2003-07-24 17:42                   ` Steven Cole
2003-07-24 16:03             ` Bas Mevissen
2003-07-24 16:05             ` Steven Cole
2003-07-24 23:15             ` Bill Davidsen
2003-07-24 23:24             ` CaT [this message]
2003-07-25  2:59               ` jw schultz
2003-07-25  3:33                 ` Miles Bader
2003-07-24 15:24         ` [OT] " Sean Neakums
2003-07-23 20:24 ` 2.6.0-test1-ac3 still broken on Adaptec I2O Alan Cox
2003-07-23 21:20   ` Samuel Flory
2003-07-23 22:17     ` Alan Cox
2003-07-24  8:01       ` Christoph Hellwig
2003-07-24 11:24         ` Alan Cox
2003-07-24 17:37 Posting format Mudama, Eric
2003-07-24 18:57 John Bradford
2003-07-25 18:49 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25 20:35 John Bradford
2003-07-25 22:10 ` jw schultz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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 NNTP newsgroup(s).