From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38497@debbugs.gnu.org
Subject: bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't
Date: Sat, 14 Dec 2019 20:22:11 +0800 [thread overview]
Message-ID: <87blsbcd1o.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <83a77v6spt.fsf@gnu.org>
> How about "M-x redraw-display RET" -- does that redraw the frame?
Nope.
I only managed to trigger the real redraw (not just the scroll bars) by
toggling the maximised state of the frame. Once I unmaximise the frame
the frame text and cursor are redrawn. Re-maximised is redrawn normally
even if I try to toggle menu-bar-mode multiple times again.
Best,
Ihor
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ihor Radchenko <yantar92@gmail.com>
>> Date: Sat, 14 Dec 2019 17:38:38 +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.
>
> How about "M-x redraw-display RET" -- does that redraw the frame?
next prev parent reply other threads:[~2019-12-14 12:22 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blsbcd1o.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=yantar92@gmail.com \
--cc=38497@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.