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: Mon, 16 Dec 2019 10:14:46 +0100	[thread overview]
Message-ID: <d3bc9445-d333-5e4d-f82d-355431d4dd4b@gmx.at> (raw)
In-Reply-To: <87mubtngt7.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>

 > I tested several more times. It's not really maximising, but the frame
 > size definitely changes (sometimes increases, sometimes decreases).
 > See the attached illustration.
 >
 >> The title bar there looks normal to me, not doubled.  And how would
 >> you know in the first place that the title bar was not redrawn?
 >
 > See the illustration.

These caps are much better, many thanks.  Maybe they can serve to
identify future problems with the double buffering issue (which IIUC
is at the core of the problems you describe).

 >>   > When I remove the call, there is still no redrawing. Moreover, without
 >>   > maximising the frame, when emacs frame is a single frame in a tile
 >>   > layout, the frame occupies all the space as if frame-resize-pixelwise
 >>   > was nil
 >>
 >> This must be a misunderstanding.  Among others, it's one purpose of
 >> 'frame-resize-pixelwise' _non-nil_ to make the frame occupy all the
 >> space.
 >
 > Note that in all the tests in that message I had frame-resize-pixelwise
 > nil. The frame occupied all the space in that scenario because I removed
 > the code responsible for setting the calculated frame size.

I was only bothered by "the frame occupies all the space as if
frame-resize-pixelwise was nil" which is misleading because
`frame-resize-pixelwise' nil implies the frame need not occupy all
space when the workarea size is not a multiple of the base character
size.

martin





  parent reply	other threads:[~2019-12-16  9:14 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 [this message]
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
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=d3bc9445-d333-5e4d-f82d-355431d4dd4b@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).