From: storm@cua.dk (Kim F. Storm)
Cc: gmorris@ast.cam.ac.uk
Subject: [Glenn Morris <gmorris@ast.cam.ac.uk>] frame-height and make-frame inconsistency
Date: 02 Apr 2003 00:47:55 +0200 [thread overview]
Message-ID: <5xbrzp96n8.fsf@kfs2.cua.dk> (raw)
Glenn Morris has found a case where the previously inactive code
that "adds height of tool-bar to frame height" causes problems.
>
> In the current CVS, the value returned by frame-height does not seem
> to be consistent with that used by make-frame.
>
> To reproduce:
>
> mv ~/.Xdefaults ~/.Xdefaults.off (if applicable)
>
> emacs -q --no-site-file
>
> (make-frame `(,(cons 'width (frame-width))
> ,(cons 'height (frame-height))))
>
> Under 21.3, the new frame has the same dimensions as the old frame.
> Under 21.3.50, the new one is taller (by the height of the tool-bar, AFAICS).
>
>
> Configuration options in both cases (i686-pc-linux-gnu, X toolkit):
>
> --without-xim --with-x --with-x-toolkit=athena --without-toolkit-scroll-bars
It would seem that the automatic resizing should only be applied to
the initial frame, but then C-x 5 f doesn't make a frame of the same
size as the initial frame.
Maybe the proper fix is to let frame-height return the height excl.
the tool-bar.
Actually, a superficial skimming through various pieces of lisp code
seem to assume that frame-height doesn't include the tool-bar height,
so maybe it would be more appropriate for frame-parameters to return
the height excl. the tool-bar height.
The change is simple, but I'm not sure what the implications are...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next reply other threads:[~2003-04-01 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 22:47 Kim F. Storm [this message]
2003-04-07 17:22 ` [Glenn Morris <gmorris@ast.cam.ac.uk>] frame-height andmake-frame inconsistency Richard Stallman
2003-04-08 16:18 ` [Glenn Morris <gmorris@ast.cam.ac.uk>] frame-height and make-frame inconsistency Kim F. Storm
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=5xbrzp96n8.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=gmorris@ast.cam.ac.uk \
/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).