unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 16 Dec 2019 11:10:41 +0800	[thread overview]
Message-ID: <87immhnexa.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <83y2vd62d6.fsf@gnu.org>

> One possible reason for not clearing the frame is that you have
> double-buffering enabled.  Can you disable it and try again?  (If you
> don't know how, search for "double buffering" in etc/NEWS.26.)

I tried to disable double buffering.
Running emacs -Q --eval "(add-to-list 'default-frame-alist
'(inhibit-double-buffering . t))", the redrawing works without any
issues.

Now, I am wondering if the issue I reported is just specific to my
system or others can also reproduce it with emacs compiled with xft,
cairo, and lucid enabled. If so, would it make sense to disable double
buffering by default for this combination of build options?

Best,
Ihor

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Ihor Radchenko <yantar92@gmail.com>
>> Cc: rudalics@gmx.at, 38497@debbugs.gnu.org
>> Date: Sun, 15 Dec 2019 21:43:34 +0800
>> 
>> > That's unheard of.  Does redraw-display at least blank the entire
>> > frame?
>> 
>> Nope. I don't see anything changing. 
>
> That's impossible.  When you invoke redraw-display, Emacs on X calls
> the function x_clear_frame, which calls x_clear_window, which calls
> XClearWindow.  Do you see this sequence of calls if you step through
> the code with a derbugger?
>
> One possible reason for not clearing the frame is that you have
> double-buffering enabled.  Can you disable it and try again?  (If you
> don't know how, search for "double buffering" in etc/NEWS.26.)
>
> Failing that, the only way I can explain this is that you have some
> "optimization" feature in your video hardware and/or driver, and that
> is the cause of all the problems you report in this thread.  Please
> review the settings of your video driver software, and turn off any
> "optimization" or "advanced" feature you find there.  If that doesn't
> help, maybe upgrading to a newer version of the video driver will
> help.






  reply	other threads:[~2019-12-16  3:10 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 [this message]
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

  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=87immhnexa.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 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).