From: "Robert J. Chassell" <bob@rattlesnake.com>
To: emacs-devel@gnu.org
Subject: Re: Man-width on terminals
Date: Thu, 8 Nov 2007 03:04:04 +0000 (UTC) [thread overview]
Message-ID: <m1Ipxga-002K4AC@rattlesnake.com> (raw)
In-Reply-To: <87ejf17e85.fsf@jurta.org> (message from Juri Linkov on Thu, 08 Nov 2007 02:54:52 +0200)
... allow terminals using all available horizontal space ...
That does not make much sense since the fix does not seem to increase
inter-line whitespace along with line length.
The purpose of limiting line lengths is to prevent needing too much
inter-line whitespace.
Readers tend to lose track of where they are -- unless there is enough
inter-line white space for whatever length of line they use. This
does not apply to all readers, of course, just to most. Printers have
found that out over the past five hundred years. That is why books
have lines that are no more than twice or so the length of an alphabet
(that measure is an old printer's rule of thumb).
With more inter-line whitespace, you can have longer lines. The
maximum reasonable length for the contents of a line with lots of
inter-line whitespace turned out to be about 70 characters. Computer
terminals have the whitespace needed, so they are seldom narrow. And,
for the same reason, terminals seldom had more than 80 characters.
(That is also why cards on which FORTRAN was written had only 80
characters.)
Of course, if you wish to make your manual page width be less than 70
characters, that is fine. I am against long lines that need more
inter-line whitespace than many writers provide.
--
Robert J. Chassell GnuPG Key ID: 004B4AC8
bob@rattlesnake.com bob@gnu.org
http://www.rattlesnake.com http://www.teak.cc
next prev parent reply other threads:[~2007-11-08 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 0:54 Man-width on terminals Juri Linkov
2007-11-08 3:04 ` Robert J. Chassell [this message]
2007-11-09 0:54 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1Ipxga-002K4AC@rattlesnake.com \
--to=bob@rattlesnake.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.