From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: Source code formatting: line length limit?
Date: Sat, 25 Jan 2003 13:26:33 +0000 (UTC) [thread overview]
Message-ID: <m18cQKP-000IeIC@localhost> (raw)
In-Reply-To: <84ptqlflp7.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de)
Until recently, I've implicitly assumed that lines should not exceed
79 or so columns.
70 columns is better, since that length enables readers to quote you
readily and to send easily readable patches.
Moreover, over the past half millenium, printers have found that
people have difficulty swinging their eyes down to the next line when
the line is too long or when the between-line spacing is too wide or
too narrow. A fill-column of 70 works well with the usual
between-line spacing on a computer screen. (Shorter lines work well
with the usual between-line spacing of printed books.)
As
File: elisp, Node: Margins
says
As a practical matter, if you are writing text for other people
to read, you should set `fill-column' to no more than 70.
Otherwise the line will be too long for people to read
comfortably, and this can make the text seem clumsy.
....
The default value for `default-fill-column' is 70.
While these remarks apply to people writing sentences and paragraphs,
they also apply to people writing code.
--
Robert J. Chassell Rattlesnake Enterprises
http://www.rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.teak.cc bob@gnu.org
next prev parent reply other threads:[~2003-01-25 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 12:39 Source code formatting: line length limit? Kai Großjohann
2003-01-25 13:26 ` Robert J. Chassell [this message]
2003-01-26 1:21 ` Stefan Monnier
2003-01-26 13:12 ` Robert J. Chassell
2003-01-27 2:32 ` Richard Stallman
2003-01-27 14:14 ` Stefan Monnier
2003-01-26 14:48 ` Kai Großjohann
2003-01-26 18:49 ` Robert J. Chassell
2003-01-27 2:32 ` Richard Stallman
2003-01-27 13:01 ` Stefan Monnier
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=m18cQKP-000IeIC@localhost \
--to=bob@rattlesnake.com \
--cc=bob@gnu.org \
--cc=emacs-devel@gnu.org \
/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.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).