From: Ihor Radchenko <yantar92@gmail.com>
To: martin rudalics <rudalics@gmx.at>, 38497@debbugs.gnu.org
Subject: bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't
Date: Sun, 15 Dec 2019 21:57:24 +0800 [thread overview]
Message-ID: <874ky1669n.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <b50d22ca-c06d-1f59-fdc8-7d8a0dbaa960@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
> You say yours is a tiling window manager: What happens when you manage
> to remove all windows but the Emacs window from display? This should
> implicitly maximise the frame. Does it redraw then?
If I do this, there is a gap below the emacs frame.
Invoking M-x menu-bar-mode resizes the frame to actual maximised state
without the gap and the redrawing works. However, the very bottom part
of the frame (that's where by title bar is located) is not being
redrawn. It's like all the frame canvas before resizing is shifted up as
much as the height of the menu-bar was without redrawing whatever was
below that size (see the attached).
> And what happens when you remove the entire
>
> XtVaSetValues (wmshell,
> XtNbaseWidth, (XtArgVal) base_width,
> XtNbaseHeight, (XtArgVal) base_height,
> XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 1 : cw),
> XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 1 : ch),
> XtNminWidth, (XtArgVal) base_width,
> XtNminHeight, (XtArgVal) base_height,
> NULL);
>
> call?
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 and M-x menu-bar-mode results in no redrawing.
Best,
Ihor
[-- Attachment #2: shift.png --]
[-- Type: image/png, Size: 8360 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1319 bytes --]
martin rudalics <rudalics@gmx.at> writes:
> >>> Two additional things you could try: What happens when you use 0
> >>> instead of 1 in the XtNwidthInc and XtNheightInc assignments like
> >>>
> >>> XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 0 : cw),
> >>> XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 0 : ch),
> >>>
> >>> And what happens when you skip these two assignments entirely when
> >>> frame_resize_pixelwise is non-nil?
> >>
> >> Let me try and report back once I finish.
> >
> > I tried both. I do not see any difference. Still no redrawing.
>
> We are probably missing something all too obvious (for example, why
> scroll bars are apparently redrawn orderly).
>
> You say yours is a tiling window manager: What happens when you manage
> to remove all windows but the Emacs window from display? This should
> implicitly maximise the frame. Does it redraw then?
>
> And what happens when you remove the entire
>
> XtVaSetValues (wmshell,
> XtNbaseWidth, (XtArgVal) base_width,
> XtNbaseHeight, (XtArgVal) base_height,
> XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 1 : cw),
> XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 1 : ch),
> XtNminWidth, (XtArgVal) base_width,
> XtNminHeight, (XtArgVal) base_height,
> NULL);
>
> call?
>
> martin
next prev parent reply other threads:[~2019-12-15 13: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 [this message]
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
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=874ky1669n.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=yantar92@gmail.com \
--cc=38497@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).