From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: darthandrus@gmail.com, 11070@debbugs.gnu.org
Subject: bug#11070: 24.0.94; Large stippled images not displayed consistently
Date: Sun, 29 Sep 2019 20:33:54 +0200 [thread overview]
Message-ID: <874l0var59.fsf@gnus.org> (raw)
In-Reply-To: <83ftkffhzq.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Sep 2019 14:40:25 +0300")
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> Then some redisplay optimization is at work here. If your build was
> configured with --enable-checking=glyphs, does the problem go away if
> you set _all_ of the following variable non-nil?
>
> inhibit-try-cursor-movement
> inhibit-try-window-id
> inhibit-try-window-reusing
No, that doesn't change anything.
But I now see more clearly what's not being updated -- it copies all the
bits in the background on the line that's being moved.
Here's the display first:
[-- Attachment #2: stip1.jpg --]
[-- Type: image/jpeg, Size: 86798 bytes --]
[-- Attachment #3: Type: text/plain, Size: 98 bytes --]
Then I hit RET before the first line. The entire line moves down,
background stipples and all:
[-- Attachment #4: stip2.jpg --]
[-- Type: image/jpeg, Size: 83777 bytes --]
[-- Attachment #5: Type: text/plain, Size: 13 bytes --]
And again:
[-- Attachment #6: stip3.jpg --]
[-- Type: image/jpeg, Size: 88263 bytes --]
[-- Attachment #7: Type: text/plain, Size: 104 bytes --]
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-29 18:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 21:12 bug#11070: 24.0.94; Large stippled images not displayed consistently Ivan Andrus
2012-03-23 10:30 ` Eli Zaretskii
2012-03-23 11:00 ` Ivan Andrus
2012-03-23 16:04 ` Eli Zaretskii
2012-03-23 18:32 ` Drew Adams
2012-03-23 23:27 ` Johan Bockgård
2012-03-23 23:33 ` Glenn Morris
2019-09-26 17:30 ` Lars Ingebrigtsen
2019-09-28 9:55 ` Eli Zaretskii
2019-09-28 19:53 ` Lars Ingebrigtsen
2019-09-29 6:03 ` Eli Zaretskii
2019-09-29 11:11 ` Lars Ingebrigtsen
2019-09-29 11:40 ` Eli Zaretskii
2019-09-29 18:33 ` Lars Ingebrigtsen [this message]
2019-09-29 19:26 ` Eli Zaretskii
2019-09-29 19:29 ` Lars Ingebrigtsen
2019-09-30 5:58 ` Eli Zaretskii
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=874l0var59.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11070@debbugs.gnu.org \
--cc=darthandrus@gmail.com \
--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).