From: "Jan D." <jan.h.d@swipnet.se>
To: martin rudalics <rudalics@gmx.at>
Cc: "19482@debbugs.gnu.org" <19482@debbugs.gnu.org>
Subject: bug#19482: Changing to big font cause display problem
Date: Fri, 27 Feb 2015 21:29:29 +0100 [thread overview]
Message-ID: <83C4500A-4001-49C5-8670-6678BEC58DAC@swipnet.se> (raw)
In-Reply-To: <54F0CA67.4050608@gmx.at>
Hi.
> 27 feb 2015 kl. 20:49 skrev martin rudalics <rudalics@gmx.at>:
>
> >> (1) `x-frame-geometry' reports an external border width of zero for a
> >> normal, non-maximized frame. That's clearly wrong, the width is 5
> >> pixels. I have no idea how to track down what XGetWindowAttributes
> >> retrieves here.
> >
> > As I said in another mail, this is probably the window manager decorations, not a window border. 5 pixels is a large window border, but a reasonable window manager decoration.
> > However, I added the window manager window border to the calculations, but I suspect it is 0 all the time.
> > In theory it could be something else.
>
> In my book the border is that thing I have to drag in order to resize a
> window with the mouse. Is that wrong? Does that mean that the border
> reported by XGetWindowAttributes is not the same as the border reported
> by XGetGeometry? In this case we should probably not ignore the eight
> argument of the latter.
The thing you drag to resize is not the X11 window border, it is a decoration drawn by the window manager in the window manager window. The border from XGetGeometry is the same as the one in XGetWindowAttributes.
Jan D.
next prev parent reply other threads:[~2015-02-27 20:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 15:21 bug#19482: Changing to big font cause display problem 张海君
2015-02-13 18:28 ` martin rudalics
2015-02-18 11:19 ` 张海君
2015-02-18 14:05 ` martin rudalics
2015-02-19 1:59 ` 张海君
2015-02-19 6:57 ` martin rudalics
2015-02-20 10:23 ` 张海君
2015-02-20 18:21 ` martin rudalics
2015-02-21 1:33 ` 张海君
2015-02-21 11:44 ` martin rudalics
2015-02-22 2:57 ` 张海君
2015-02-22 10:00 ` martin rudalics
2015-02-22 10:54 ` 张海君
2015-02-22 11:32 ` martin rudalics
2015-02-22 12:27 ` 张海君
2015-02-22 17:09 ` martin rudalics
2015-02-23 2:11 ` 张海君
2015-02-22 16:27 ` Jan D.
2015-02-22 17:10 ` martin rudalics
2015-02-22 17:43 ` Jan D.
2015-02-22 18:52 ` martin rudalics
2015-02-23 6:22 ` Jan D.
2015-02-24 19:09 ` Jan D.
2015-02-25 7:34 ` martin rudalics
2015-02-25 9:20 ` Jan D.
2015-02-25 10:33 ` martin rudalics
2015-02-25 15:27 ` Jan D.
2015-02-25 17:33 ` martin rudalics
2015-02-25 18:25 ` Jan D.
2015-02-25 19:00 ` martin rudalics
2015-02-25 20:22 ` Jan D.
2015-02-27 8:30 ` martin rudalics
2015-02-27 17:49 ` Jan D.
2015-02-25 19:17 ` Jan D.
2015-02-27 8:30 ` martin rudalics
2015-02-27 17:52 ` Jan D.
2015-02-27 19:49 ` martin rudalics
2015-02-27 20:29 ` Jan D. [this message]
2015-03-01 15:14 ` martin rudalics
2015-03-01 16:18 ` Jan D.
2015-03-10 14:36 ` 张海君
2015-03-10 18:47 ` martin rudalics
2015-03-12 5:14 ` Jan D.
2015-03-12 10:13 ` martin rudalics
2015-03-12 16:52 ` Eli Zaretskii
2015-03-12 18:21 ` Jan D.
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=83C4500A-4001-49C5-8670-6678BEC58DAC@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=19482@debbugs.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).