From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 57475@debbugs.gnu.org
Subject: bug#57475: 29.0.50; Position problem with make-frame on Lucid build
Date: Tue, 30 Aug 2022 10:19:21 +0200 [thread overview]
Message-ID: <87ilmaw3cm.fsf@gmx.net> (raw)
In-Reply-To: <87ler6pkc0.fsf@yahoo.com> (Po Lu's message of "Tue, 30 Aug 2022 09:54:23 +0800")
On Tue, 30 Aug 2022 09:54:23 +0800 Po Lu <luangruo@yahoo.com> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> On a Lucid build, make-frame appears to ignore the frame parameters
>> (left . 0) and (top . 0), when passed individually or together:
>
> Please show the value of running "xprop WM_NORMAL_HINTS", and then
> clicking on the frame in question after the cursor changes to a
> crosshair.
Here's the output immediately after executing emacs -Q:
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified size: 674 by 676
program specified minimum size: 34 by 66
program specified resize increment: 8 by 17
program specified base size: 34 by 66
window gravity: NorthWest
And here's the output immediately after evaluating
(make-frame '((left . 0) (top . 0))) in the new frame:
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified size: 658 by 650
program specified minimum size: 34 by 66
program specified resize increment: 8 by 17
program specified base size: 34 by 66
window gravity: NorthWest
Steve Berman
next prev parent reply other threads:[~2022-08-30 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 11:51 bug#57475: 29.0.50; Position problem with make-frame on Lucid build Stephen Berman
2022-08-30 1:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 8:19 ` Stephen Berman [this message]
2022-08-30 10:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 10:20 ` Stephen Berman
[not found] ` <87czcivxre.fsf@gmx.net>
[not found] ` <87v8q9m9yr.fsf@yahoo.com>
2022-08-31 7:53 ` Stephen Berman
2022-09-01 13:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87ilmaw3cm.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=57475@debbugs.gnu.org \
--cc=luangruo@yahoo.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).