GNU bug report logs - #38497
27.0.50; Frame is not rendered when frame-resize-pixelwise it 't

Previous Next

Package: emacs;

Reported by: 'Ihor Radchenko' <yantar92 <at> gmail.com>

Date: Thu, 5 Dec 2019 07:11:02 UTC

Severity: normal

Found in version 27.0.50

Done: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>

Bug is archived. No further changes may be made.

Full log

Message #83 received at 38497 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>, 38497 <at> debbugs.gnu.org
Subject: Re: bug#38497: 27.0.50; Frame is not rendered when
 frame-resize-pixelwise it 't
Date: Sat, 14 Dec 2019 17:39:35 +0800

> OK.  So we have a simpler scenario now.  From the screenshot I cannot
> understand where redrawing hangs.  Is input still functional in such a
> mangled frame?  Does evaluating (redisplay t) change anything?

The input is functional. I can split windows with C-x 2/3. The frame is
partially redrawn (just the scroll bars, as in the screenshot).
Blindly running (redisplay t) does nothing.

> 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.

Best,
Ihor

martin rudalics <rudalics <at> gmx.at> writes:

>  > I mean literally. Emacs frame does not redraw properly. I tried make
>  > several window splits after M-x menu-bar-mode. See the attached
>  > screenshot.
>  >
>  > I don't even need to change fonts or load emacs theme to trigger this.
>
> OK.  So we have a simpler scenario now.  From the screenshot I cannot
> understand where redrawing hangs.  Is input still functional in such a
> mangled frame?  Does evaluating (redisplay t) change anything?
>
> 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?
>
> martin
This bug report was last modified 5 years and 139 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.