From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 14795@debbugs.gnu.org
Subject: bug#14795: height parameter inconsistent in new vs existing frames when tool-bar is enabled
Date: Fri, 05 Jul 2013 09:45:31 +0200 [thread overview]
Message-ID: <51D6799B.4000303@gmx.at> (raw)
In-Reply-To: <CAAeL0SR+VFyV7hY3fX=_ZteY6-jHmfkL8dpFu28GCfYC6u8UJw@mail.gmail.com>
> /* Add the tool-bar height to the initial frame height so that the
> user gets a text display area of the size he specified with -g or
> via .Xdefaults. Later changes of the tool-bar height don't
> change the frame size. This is done so that users can create
> tall Emacs frames without having to guess how tall the tool-bar
> will get. */
> if (toolbar_p && FRAME_TOOL_BAR_LINES (f))
>
> I remain unconvinced. That's mixing apples and oranges. If UI commands
> (like -g) and UI settings (like X resources) should interpret the
> frame height as meaning the client area, so be it. But then we should
> decouple these from the `height' frame parameter, because it doesn't
> really make sense to say that `height' means client area height when
> creating a frame, but total frame height when modifying it.
What did you expect? It's impossible to tell what a frame's height or
width is :-(
martin
next prev parent reply other threads:[~2013-07-05 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 22:52 bug#14795: height parameter inconsistent in new vs existing frames when tool-bar is enabled Juanma Barranquero
2013-07-04 23:11 ` Juanma Barranquero
2013-07-05 7:45 ` martin rudalics [this message]
2013-07-05 9:51 ` Juanma Barranquero
2013-07-05 9:29 ` Jan Djärv
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=51D6799B.4000303@gmx.at \
--to=rudalics@gmx.at \
--cc=14795@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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).