unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Ihor Radchenko <yantar92@gmail.com>, 38497@debbugs.gnu.org
Subject: bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't
Date: Sun, 8 Dec 2019 09:57:51 +0100	[thread overview]
Message-ID: <15ff2306-02dd-ea0c-d5e0-ccc6de865c22@gmx.at> (raw)
In-Reply-To: <87muc3bf9q.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>

 >> ... If not, can you tell me the four values here
 >> when it fails to redraw - that of FRAME_PIXEL_WIDTH (f), pixel_width,
 >> FRAME_PIXEL_HEIGHT (f) and pixel_height.
 >
 > Not sure how to get those.

By running Emacs under the debugger and putting a breakpoint at that
position.  But let's put that aside for the moment since, as you say,
this part is not the real cause of the problem anyway.

 > Actually, this piece of code seems to be a more specific reason
 > triggering the bug (see the relevant patch attached - that patch makes
 > the bug disappear).

Unfortunately, that patch breaks pixelwise resizing.  The frame could
then be resized only in character size increments, defeating the entire
original purpose of 'frame-resize-pixelwise'.

 > I tried your suggestion (no idea how it is different from original code
 > though). It makes no difference.

I would have been surprised if it did.

 > A possible hint to why this code fails to resize the frame is that my
 > WM resizes the frame as soon as it is created. It is not a gradual
 > resizing with mouse, but rather instant resize to pre-calculated size
 > (according to layout). I can sometimes even see the frame being created
 > with much smaller size for a split second followed by resizing it to
 > target size.

How do you create such a frame in the first place?

martin





  reply	other threads:[~2019-12-08  8:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  7:08 bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't 'Ihor Radchenko'
2019-12-05  9:10 ` martin rudalics
2019-12-05 10:21   ` Ihor Radchenko
2019-12-05 13:45     ` martin rudalics
2019-12-07 13:35       ` Ihor Radchenko
2019-12-07 16:29         ` martin rudalics
2019-12-07 16:58           ` Ihor Radchenko
2019-12-08  8:57             ` martin rudalics
2019-12-08  9:24               ` Ihor Radchenko
2019-12-09  9:20                 ` martin rudalics
2019-12-13  7:18                   ` Ihor Radchenko
2019-12-13  7:18                   ` Ihor Radchenko
2019-12-13  7:03               ` Ihor Radchenko
2019-12-13  9:35                 ` martin rudalics
2019-12-13 11:42                   ` Ihor Radchenko
2019-12-13 15:57                     ` martin rudalics
2019-12-13 16:46                       ` Ihor Radchenko
2019-12-14  9:06                         ` martin rudalics
2019-12-14  9:38                           ` Ihor Radchenko
2019-12-14 11:40                             ` Eli Zaretskii
2019-12-14 12:22                               ` Ihor Radchenko
2019-12-14 13:36                                 ` Eli Zaretskii
2019-12-15 13:43                                   ` Ihor Radchenko
2019-12-15 15:21                                     ` Eli Zaretskii
2019-12-16  3:10                                       ` Ihor Radchenko
2019-12-16  3:33                                         ` Eli Zaretskii
2019-12-14  9:39                           ` Ihor Radchenko
2019-12-14 10:16                             ` Ihor Radchenko
2019-12-14 13:24                               ` martin rudalics
2019-12-15 13:57                                 ` Ihor Radchenko
2019-12-15 17:42                                   ` martin rudalics
     [not found]                                     ` <87mubtngt7.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>
2019-12-16  9:14                                       ` martin rudalics
2019-12-16 10:53                                       ` mituharu
2019-12-16 13:04                                         ` Ihor Radchenko
2019-12-16 15:36                                           ` Eli Zaretskii
2019-12-17  0:39                                           ` Ihor Radchenko
2019-12-17  6:50                                             ` YAMAMOTO Mitsuharu
2019-12-17 10:37                                               ` Ihor Radchenko
2020-01-06  9:19                                                 ` YAMAMOTO Mitsuharu
2020-01-06 10:57                                                   ` Ihor Radchenko
2020-01-07  3:52                                                     ` YAMAMOTO Mitsuharu
2019-12-08  4:41           ` Ihor Radchenko
2019-12-08  8:57             ` martin rudalics [this message]
2019-12-08  9:21               ` Ihor Radchenko
2019-12-09  9:19                 ` martin rudalics
2019-12-09  9:55                   ` Ihor Radchenko
2019-12-09 15:59                     ` martin rudalics
2019-12-13  7:19                       ` Ihor Radchenko

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=15ff2306-02dd-ea0c-d5e0-ccc6de865c22@gmx.at \
    --to=rudalics@gmx.at \
    --cc=38497@debbugs.gnu.org \
    --cc=yantar92@gmail.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).