unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Micah Cowan <micah@cowan.name>
Subject: Re: auto-fill mode in java-mode
Date: 19 Oct 2003 02:07:31 -0700	[thread overview]
Message-ID: <m3n0bxwq7g.fsf@localhost.localdomain> (raw)
In-Reply-To: mailman.1944.1066497425.21628.help-gnu-emacs@gnu.org

Adam Hardy <emacs@cyberspaceroad.com> writes:

> Actually is 72 the standard email line length? As I said earlier,
> my requirement is to have all the code easily emailable without
> being rewrapped by the email software.

RFC 822, which defines the format of email messages (or did until
it was replaced by RFC 2822), notes that "long lines" is commonly
understood to be lines that are "greater than 65 or 72
characters." RFC 2822 says that a line "SHOULD be no more than
78 characters, excluding the CRLF." RFC 1855, "Netiquette
Guidelines", Section 2.1.1 ("For mail") requests that line length
be limited to "fewer than 65 characters."

Keeping line length under 65 also allows several levels of
quoting prefixes before overflow becomes a danger; for this
reason, I keep my fill-column set to 65.

-Micah

  parent reply	other threads:[~2003-10-19  9:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1541.1065910097.21628.help-gnu-emacs@gnu.org>
2003-10-13  9:10 ` auto-fill mode in java-mode Alan Mackenzie
2003-10-13 21:58   ` Adam Hardy
     [not found]   ` <mailman.1632.1066082371.21628.help-gnu-emacs@gnu.org>
2003-10-16 21:16     ` Alan Mackenzie
2003-10-17  9:38       ` Adam Hardy
2003-10-17 14:49       ` Stefan Monnier
2003-10-18 17:15         ` Adam Hardy
     [not found]         ` <mailman.1944.1066497425.21628.help-gnu-emacs@gnu.org>
2003-10-18 21:03           ` Johan Bockgård
2003-10-18 21:23           ` lawrence mitchell
2003-10-19  9:07           ` Micah Cowan [this message]
2003-10-11 22:07 Adam Hardy

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m3n0bxwq7g.fsf@localhost.localdomain \
    --to=micah@cowan.name \
    /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).