unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Fiander <david@fiander.info>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 64809@debbugs.gnu.org
Subject: bug#64809: 29.1; Initial frame is wrong size when dimensions specified in init file
Date: Mon, 24 Jul 2023 08:55:49 -0500	[thread overview]
Message-ID: <724dd8b2-ca9a-6ac6-15cb-63671a679984@fiander.info> (raw)
In-Reply-To: <87fs5d1lsw.fsf@yahoo.com>



On 2023-07-24 08:27, Po Lu wrote:
> David Fiander <david@fiander.info> writes:
> 
>> On 2023-07-24 07:05, Po Lu wrote:
>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>
>>>>> Date: Sun, 23 Jul 2023 15:02:45 -0500
>>>>> From: David Fiander <david@fiander.info>
>>>>>
>>>>> Using the below init file, and running emacs from the command line, the
>>>>> initial frame seems to appear with the correct size but then shrinks
>>>>> down.
>>>>
>>>> Shrinks down to what size?
>>
>> When I resize the window, the emacs tooltip says that it's
>> 89x25. xwininfo says that it's 752x504 pixels. The characters
>> displayed in the window are the same size as when I run 28.2. See the
>> attached screenshot.
>>
>> When I use the same init file with emacs 28.2, the emacs tooltip also
>> says 89x25, but xwininfo reports that it is 1215x824 pixels
> 
> What happens if you set:
> 
>    (setq frame-resize-pixelwise t)
> 
> in your early-init.el?

The same "small window" behaviour.
> 
>> I'm using gtk+, but not pgtk. The window manager is XFCE.
> 
> Thanks.  Does the problem still occur with a no-toolkit build (one with
> --with-x-toolkit=no?)

both with and with frame-resize-pixelwise, the window appears "full 
size", blinks to the small size, and the resizes correctly for the given 
font.





  reply	other threads:[~2023-07-24 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 20:02 bug#64809: 29.1; Initial frame is wrong size when dimensions specified in init file David Fiander
2023-07-24 11:27 ` Eli Zaretskii
2023-07-24 12:05   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-24 13:15     ` David Fiander
2023-07-24 13:27       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-24 13:55         ` David Fiander [this message]
2023-07-24 23:50           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-24 16:33         ` Jim Porter
2023-07-24 20:53           ` Jim Porter
2023-07-25  0:09             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-25  0:36               ` David Fiander
2023-07-25  1:14               ` Jim Porter
2023-07-25  2:08                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-25 11:56                   ` Eli Zaretskii
2023-07-25 15:42                     ` Jim Porter
2023-07-25 16:27                       ` David Fiander

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=724dd8b2-ca9a-6ac6-15cb-63671a679984@fiander.info \
    --to=david@fiander.info \
    --cc=64809@debbugs.gnu.org \
    --cc=eliz@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).