unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <bob@rattlesnake.com>, <emacs-devel@gnu.org>
Subject: RE: patch to fill `Parent documentation...' in Customize, plus two related suggestions
Date: Fri, 28 Dec 2007 15:04:24 -0800	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACKEALCGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <m1J8Nyv-002K4LC@rattlesnake.com>

>     ... making a Customize frame wider than it needs to be.
>
> How can you make any frame wider than what was set it your .emacs file
> and in your start up options?  You are right, it is a definite bug if
> it does do that.

`set-frame-size' resizes a frame. It is not limited by your
`initial-frame-alist' or `default-frame-alist' or any other such alist.

I said, in this regard, that such a long line "can throw off window-fitting
and frame-fitting code". If you have code fits the width of a window or
frame to the longest line in a buffer, then the window or frame will be as
long as that longest line.

That is my case. I call `set-frame-size' to fit one-window-p frames to their
buffer text. For the target height, frame-fitting counts lines. For the
target width, it uses the length of the longest line.

A doc string generally has lines that are no longer than 80 columns. A
250-column line is an outlying exception; it throws things off quite a bit.
The result is a very wide frame, with much wasted space at the right.

A doc string generally respects a max line length, by convention, but this
particular line falls through the cracks because it is written by code that
doesn't take the recommended max into account.

  reply	other threads:[~2007-12-28 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 19:04 patch to fill `Parent documentation...' in Customize, plus two related suggestions Drew Adams
2007-12-28 22:47 ` Robert J. Chassell
2007-12-28 23:04   ` Drew Adams [this message]
2007-12-30  1:36 ` Richard Stallman
2007-12-30  2:13   ` Drew Adams
2007-12-31 14:42     ` Richard Stallman
2007-12-30  1:36 ` Richard Stallman

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=BNELLINCGFJLDJIKDGACKEALCGAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=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 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).