unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: "Kai Großjohann" <kai.grossjohann@uni-duisburg.de>
Subject: Re: Source code formatting: line length limit?
Date: Sat, 25 Jan 2003 20:21:33 -0500	[thread overview]
Message-ID: <200301260121.h0Q1LXx18015@rum.cs.yale.edu> (raw)
In-Reply-To: m18cQKP-000IeIC@localhost

> 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.)

Note that in source code, most lines don't start in column 0, so for
a given line, the number of columns of text is not necessarily the same
as the column of the rightmost char.

I happen to think that 60 columns is more legible, but I also think
that in most cases, source code that spans 80 columns is perfectly legible
because almost none of the lines actually takes more than 60 columns
of text.  Also the non-constant indentation of the code also helps
your eyes find the next line.

And since I find vertical screen-real-estate to be at a premium, I advocate
using all 80 columns for code (text is obviously another matter).


	Stefan

  reply	other threads:[~2003-01-26  1:21 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
2003-01-26  1:21   ` Stefan Monnier [this message]
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=200301260121.h0Q1LXx18015@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=kai.grossjohann@uni-duisburg.de \
    /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).