unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: August <fusionfive@comhem.se>
Subject: Re: Carbon emacs - frame too big for minibuffer can't resize window
Date: Wed, 02 Mar 2005 16:22:31 +0100	[thread overview]
Message-ID: <1109776951.5325.31.camel@c83-250-204-178.bredband.comhem.se> (raw)
In-Reply-To: <87sm3e6wfa.fsf-monnier+gnu.emacs.help@gnu.org>

On ons, 2005-03-02 at 08:02 -0500, Stefan Monnier wrote:
> > Note that lines longer than 80 characters are not recommended as they
> > will not fit on standard terminals. That's why the default width is 80.
> 
> The problem is not "standard terminals" but legibility.

I'm sure that legibility was one of the motivations for the decision to
use 80 character columns for terminals. The standard width sure is an
issue here as wrongly formatted paragraphs affect legibility even more
than overly long lines. The default width for editors and terminal
windows is usually 80 characters.

> The rule of thumb is usually that up to 60 columns is perfectly fine, but as
> you go further away from that (soft) limit, the eyes have a harder and harder
> time to find the beginning of a line from the end of the previous one.

(I notice that your message contains lines of length up to 77
characters.)

> Given that code (as opposed to plain text) often has some indentation on the
> left side, 80 columns is still OK (assuming 20 of them are indentation
> whitespace).
> 
> For this reason I'd indeed recommend to stick to 80 columns for typical
> situations (even though barely anybody still knows what's a "standard
> terminal").  

I guess most people have heard about the DOS prompt, terminal windows,
console mode or run-level three etc.

-- 
August

  reply	other threads:[~2005-03-02 15:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 17:25 Carbon emacs - frame too big for minibuffer can't resize window George Colpitts
2005-02-27 17:35 ` Peter Dyballa
     [not found] ` <mailman.1903.1109526710.32256.help-gnu-emacs@gnu.org>
2005-02-27 19:15   ` George Colpitts
2005-02-27 22:12 ` August
2005-02-27 22:38 ` Stefan Monnier
2005-02-27 23:25   ` Peter Dyballa
2005-02-27 23:46     ` Stefan Monnier
2005-02-28  0:17       ` Peter Dyballa
     [not found]       ` <mailman.1931.1109551850.32256.help-gnu-emacs@gnu.org>
2005-02-28  0:59         ` David Kastrup
2005-02-28  9:38           ` Peter Dyballa
2005-02-28 11:25           ` Piet van Oostrum
2005-02-28 11:47             ` David Kastrup
2005-02-28 12:56               ` Stefan Monnier
2005-02-28 12:54         ` Stefan Monnier
     [not found] ` <mailman.1926.1109544581.32256.help-gnu-emacs@gnu.org>
2005-02-28  0:46   ` George Colpitts
2005-02-28  1:49     ` Tim McNamara
2005-02-28 16:12     ` August
2005-02-28 16:40       ` Peter Dyballa
2005-02-28 17:50         ` August
2005-02-28 16:50     ` Drew Adams
     [not found]     ` <mailman.2013.1109608386.32256.help-gnu-emacs@gnu.org>
2005-03-02 13:02       ` Stefan Monnier
2005-03-02 15:22         ` August [this message]
     [not found]         ` <mailman.2325.1109778063.32256.help-gnu-emacs@gnu.org>
2005-03-04  0:29           ` Miles Bader

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=1109776951.5325.31.camel@c83-250-204-178.bredband.comhem.se \
    --to=fusionfive@comhem.se \
    /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).