From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Re: Trimming quotes Date: Sun, 30 Dec 2012 09:49:49 +0800 Message-ID: References: Reply-To: jamshark70@dewdrop-world.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8fb1fd90b5a9af04d2081cea Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44184) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tp82C-0006XX-Ur for Emacs-orgmode@gnu.org; Sat, 29 Dec 2012 20:49:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tp82B-00027u-NU for Emacs-orgmode@gnu.org; Sat, 29 Dec 2012 20:49:52 -0500 Received: from mail-ob0-f182.google.com ([209.85.214.182]:53274) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tp82B-00027n-Hx for Emacs-orgmode@gnu.org; Sat, 29 Dec 2012 20:49:51 -0500 Received: by mail-ob0-f182.google.com with SMTP id 16so10596401obc.41 for ; Sat, 29 Dec 2012 17:49:50 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: Emacs-orgmode@gnu.org --e89a8fb1fd90b5a9af04d2081cea Content-Type: text/plain; charset=ISO-8859-1 On Dec 29, 2012 11:23 PM, "Thomas S. Dye" wrote: > Can you point me to trimming guidelines for digest readers? I don't know where to find published guidelines, but this is how I try to handle it: - Quote just enough to capture the gist of what you're replying to. (As here -- I'm answering a specific question, so I quote the question and trim out the rest.) Sometimes that calls for just a couple of lines, or it might need a longer chunk (of a code example, say). The thread I pointed to would have needed some longer quotes. - Quotes from messages earlier than the one you're directly answering should be avoided, but if you need material from an older message to get the gist, keep it really really short. (E.g., if you're quoting a long code snip from the previous message, there is no need to include the same code snip in higher quote levels.) - Avoid top-posting. Top-posting allows you to ignore the amount of quoted material beyond the mail editor window's lower boundary. You have no idea if it's 30, 50, 200 or over 1000 lines. (I know some have reasons to prefer top-posting and I don't want to reopen that debate, but it seems a valid observation that excessively long quotes usually come with top-posted replies. So an alternate way to say it is: If you really want to top-post, please also review the entire contents for redundancy before sending.) hjh --e89a8fb1fd90b5a9af04d2081cea Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Dec 29, 2012 11:23 PM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
> Can you point me to trimming guidelines for digest readers?

I don't know where to find published guidelines, but thi= s is how I try to handle it:

- Quote just enough to capture the gist of what you're r= eplying to. (As here -- I'm answering a specific question, so I quote t= he question and trim out the rest.) Sometimes that calls for just a couple = of lines, or it might need a longer chunk (of a code example, say). The thr= ead I pointed to would have needed some longer quotes.

- Quotes from messages earlier than the one you're direc= tly answering should be avoided, but if you need material from an older mes= sage to get the gist, keep it really really short. (E.g., if you're quo= ting a long code snip from the previous message, there is no need to includ= e the same code snip in higher quote levels.)

- Avoid top-posting. Top-posting allows you to ignore the am= ount of quoted material beyond the mail editor window's lower boundary.= You have no idea if it's 30, 50, 200 or over 1000 lines. (I know some = have reasons to prefer top-posting and I don't want to reopen that deba= te, but it seems a valid observation that excessively long quotes usually c= ome with top-posted replies. So an alternate way to say it is: If you reall= y want to top-post, please also review the entire contents for redundancy b= efore sending.)

hjh

--e89a8fb1fd90b5a9af04d2081cea--