unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
Subject: Re: Carbon emacs - frame too big for minibuffer can't resize window
Date: Fri, 04 Mar 2005 09:29:38 +0900	[thread overview]
Message-ID: <87oee0p825.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <mailman.2325.1109778063.32256.help-gnu-emacs@gnu.org> (August's message of "Wed, 02 Mar 2005 16:22:31 +0100")

August <fusionfive@comhem.se> writes:
>> 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.

Yeah, and I strongly dislike the occasional suggestion you see to "just
make your windows wider, c'mon it's a modern system!" (hi Tom!).

My display is perfectly _capable_ of holding very wide windows, but *I
don't want such windows*!!!

My reasoning is this:  _most_ code or line-wrapped text doesn't have
long lines (for good legibility reasons), so if I make my windows very
wide by default, I'm simply going to have a lot of empty space in them
most of the time; by keeping my windows to a reasonable width, I can in
fact fit two windows side-by-side on my display, allowing me to use the
available space more productively.

-Miles
-- 
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.

      parent reply	other threads:[~2005-03-04  0:29 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
     [not found]         ` <mailman.2325.1109778063.32256.help-gnu-emacs@gnu.org>
2005-03-04  0:29           ` Miles Bader [this message]

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=87oee0p825.fsf@tc-1-100.kawasaki.gol.ne.jp \
    --to=miles@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.
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).