unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Geoff Kuenning <geoff@cs.hmc.edu>
Cc: 27923@debbugs.gnu.org
Subject: bug#27923: 24.3; -iconic switch screws up geometry
Date: Fri, 17 Nov 2017 09:53:00 +0100	[thread overview]
Message-ID: <5A0EA36C.8040904@gmx.at> (raw)
In-Reply-To: <pniwp2p95fq.fsf@bow.cs.hmc.edu>

 > One other thing: I just checked the actual width of my frame by typing
 > 80 characters, and it's 80 characters even though xwininfo is
 > reporting 79.  So I think this is either an actual xwininfo bug, or a
 > minor interaction between emacs and X that causes the character size
 > of a pixel window to be seen slightly incorrectly.

The inherent idea here is that when Emacs comes up with a one-window
frame that does not contain a minibuffer window, the sizes specified by
'frame-width' and 'frame-height' match the maximum number of characters
on one line and the maximum number of lines that can be displayed
in that frame's window.  For each and every build of Emacs on every
platform and regardless of which other GUI elements are present.

So, for example, when you add/remove scrollbars or change the default
font of a frame, Emacs usually asks the window manager to change the
size of the (window manager) window to keep the number of lines/columns
of the frame constant.

martin





  reply	other threads:[~2017-11-17  8:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 20:41 bug#27923: 24.3; -iconic switch screws up geometry Geoff Kuenning
2017-08-17  9:22 ` martin rudalics
     [not found]   ` <pniziawo843.fsf@bow.cs.hmc.edu>
2017-08-19  9:55     ` martin rudalics
2017-11-15  0:12       ` Geoff Kuenning
2017-11-16  9:04         ` martin rudalics
2017-11-16  9:13           ` Geoff Kuenning
2017-11-16  9:29             ` martin rudalics
2017-11-16 23:20               ` Geoff Kuenning
2017-11-17  8:53                 ` martin rudalics [this message]
2017-11-16 23:16           ` Geoff Kuenning
2017-11-17  8:52             ` martin rudalics
2017-11-17  8:59               ` Geoff Kuenning
2017-11-17  9:23                 ` martin rudalics
2017-11-17  9:31                   ` Geoff Kuenning
2022-02-21 15:32 ` Lars Ingebrigtsen
2022-02-21 22:53   ` Geoff Kuenning
2022-02-22  1:45     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-22 13:24     ` Lars Ingebrigtsen
2022-02-23  9:28     ` martin rudalics
2022-02-23 22:17       ` Geoff Kuenning
2022-02-24  9:16         ` Lars Ingebrigtsen
2022-02-24 17:55           ` Geoff Kuenning
2022-02-24 18:07             ` Lars Ingebrigtsen
2022-02-24  9:19         ` martin rudalics

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=5A0EA36C.8040904@gmx.at \
    --to=rudalics@gmx.at \
    --cc=27923@debbugs.gnu.org \
    --cc=geoff@cs.hmc.edu \
    /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).