From: "Drew Adams" <drew.adams@oracle.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>, <rms@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
jan.h.d@swipnet.se, bob@rattlesnake.com, emacs-devel@gnu.org
Subject: RE: [Fwd: Frame Height Different for Default Frame and AdditionalFrames]
Date: Sun, 6 Jan 2008 12:45:18 -0800 [thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACIEHECGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <jwvabniu2sz.fsf-monnier+emacs@gnu.org>
> > 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.
>
> > Ideally, the tool bar ought to work like the menu bar:
> > turning it on or off should not affect the height of the text area.
>
> Well, in my world, the The Right Thing is to not change the size of the
> frame unless explicitly requested, so adding a toolbar or menubar should
> reduce the amount of text displayed.
>
> But clearly in other worlds, the convention is different (e.g. macosx
> users probably expect the toolbar to change the size of the whole frame).
That's what I said too:
It is likely that there are different preferences for this
based on different uses of frames.
We should have a user option for this:
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
next prev parent reply other threads:[~2008-01-06 20:45 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
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 ` Drew Adams [this message]
2007-10-10 21:03 ` 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=BNELLINCGFJLDJIKDGACIEHECGAA.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=monnier@iro.umontreal.ca \
--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).