unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>, "martin rudalics" <rudalics@gmx.at>
Cc: bob@rattlesnake.com, rms@gnu.org, emacs-devel@gnu.org
Subject: RE: [Fwd: Frame Height Different for Default Frame and Additional Frames]
Date: Sat, 5 Jan 2008 10:08:49 -0800	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACCEFNCGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <477FBF6E.20307@swipnet.se>

> > Did we already settle on a "right" way to do this?  Robert expressed the
> > desire to keep the number of text lines invariant.  ISTR others wanted
> > the size of the frame on the screen stay invariant.  At least a similar
> > issue was recently brought up for menubars.  Finally, I'm interested how
> > changes of menu-bar-lines/tool-bar-lines are supposed to be applied and
> > handled - I'm quite lost in this context.
>
> I don't think we did.  But frame size can't in general stay constant as
> we have wm hints.  For example, I have 13 pixels of text height.
> That gives min resize 13.  The tool bar is 36 pixels.  So when the
> tool bar goes, either we increase text size by 3 (== 39, 3
> additional pixels) or by 2 (26, decrease by 10 pixels).
>
> I'll implement whatever seems easiest, and then people can suggest
> alternatives after that.

The fact that it is not always possible to maintain exactly the same overall
frame size because that size is not always an integral number of characters
is not a reason to not try to maintain the size as closely as possible.
Please don't simply "implement whatever seems easiest".

It is likely that there are different preferences for this based on
different uses of frames.

Someone who typically uses frames (e.g. non-nil pop-up-frames) might want
the frame size to remain the same (or as close to that as possible). Such a
user will want to fit frames, tile them, and perform other operations for
which the overall (outside) frame dimensions are significant. I and some
others are in this group.

Someone else might want the text content within the frame to remain
constant. Such a user might not care so much about the outside frame
dimensions.

The right approach to this is to provide a user option for it. There is no
sense arguing over which frame-size treatment is best in this regard, and it
does not make sense to simply code "whatever seems easiest" and then
entertain suggestions for changes after that.

Let's try to get it right now, and provide an option to let users choose the
behavior they want - different users use frames differently. We know that
character size does not always map exactly to pixel size, but that's not a
reason to not try to DTRT.

  reply	other threads:[~2008-01-05 18:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002501c8044b$fcc95390$6100000a@intermedinc.internal>
     [not found] ` <4701F8AC.6070900@gmx.at>
     [not found]   ` <E1Iewxc-0004U8-CC@fencepost.gnu.org>
2007-10-08 21:12     ` [Fwd: Frame Height Different for Default Frame and Additional Frames] martin rudalics
2007-10-09 20:02       ` Richard Stallman
2007-10-09 21:25         ` martin rudalics
2007-10-10  5:55           ` Jan Djärv
2007-10-10  6:51             ` martin rudalics
2007-10-10  7:39               ` Jan Djärv
2007-10-10  7:50                 ` Jason Rumney
2007-10-10 20:41                 ` martin rudalics
2007-10-11  6:15                   ` Jan Djärv
2007-10-11  8:52                     ` martin rudalics
2007-10-11 14:01                     ` Stefan Monnier
2007-10-14 16:29                       ` Richard Stallman
2007-10-11  5:19             ` Richard Stallman
2007-10-11  8:52               ` martin rudalics
2007-10-11 18:03                 ` Jan Djärv
2007-12-25 17:17                   ` Richard Stallman
2007-12-27 19:10                     ` martin rudalics
2007-12-28 13:56                       ` Richard Stallman
2007-12-28 20:06                         ` martin rudalics
2007-12-28 23:09                           ` Robert J. Chassell
2007-12-28 23:51                             ` martin rudalics
2008-01-05 11:22                               ` Jan Djärv
2008-01-05 13:08                                 ` martin rudalics
2008-01-05 17:33                                   ` Jan Djärv
2008-01-05 18:08                                     ` Drew Adams [this message]
2008-01-05 22:42                                       ` Robert J. Chassell
2008-01-05 23:00                                       ` Jan Djärv
2008-01-06  8:08                                   ` Richard Stallman
2008-01-06 20:19                                     ` Stefan Monnier
2008-01-06 20:45                                       ` [Fwd: Frame Height Different for Default Frame and AdditionalFrames] Drew Adams
2007-10-10 21:03           ` [Fwd: Frame Height Different for Default Frame and Additional Frames] 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=BNELLINCGFJLDJIKDGACCEFNCGAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=rms@gnu.org \
    --cc=rudalics@gmx.at \
    /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).