From: James Harkins <jamshark70@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Trimming quotes
Date: Sun, 30 Dec 2012 09:49:49 +0800 [thread overview]
Message-ID: <CAFniQ7XUs-RakfzjKqVqm9vzC+F0oDiEAfW0NhGS3Wfiv81k6A@mail.gmail.com> (raw)
In-Reply-To: <m1bodc3ms0.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
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 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
[-- Attachment #2: Type: text/html, Size: 1590 bytes --]
next prev parent reply other threads:[~2012-12-30 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 3:56 Trimming quotes James Harkins
2012-12-29 15:23 ` Thomas S. Dye
2012-12-30 1:49 ` James Harkins [this message]
2012-12-30 19:09 ` Thomas S. Dye
2012-12-31 10:12 ` Bastien
2012-12-30 4:30 ` Ben Finney
2012-12-30 5:01 ` Nick Dokos
2012-12-30 9:47 ` Ian Barton
2012-12-30 12:03 ` Ben Finney
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFniQ7XUs-RakfzjKqVqm9vzC+F0oDiEAfW0NhGS3Wfiv81k6A@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=tsd@tsdye.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).