From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: dgutov@yandex.ru, 16621@debbugs.gnu.org
Subject: bug#16621: 24.3.50; Periodic timer + overlays = flickering near point
Date: Wed, 05 Feb 2014 05:57:51 +0200 [thread overview]
Message-ID: <83ppn21a9s.fsf@gnu.org> (raw)
In-Reply-To: <76F58FD5-23A5-43EC-91FA-BAD933BB41DA@swipnet.se>
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Tue, 4 Feb 2014 23:08:13 +0100
> Cc: Dmitry Gutov <dgutov@yandex.ru>,
> "16621@debbugs.gnu.org" <16621@debbugs.gnu.org>,
> "monnier@IRO.UMontreal.CA" <monnier@IRO.UMontreal.CA>
>
> So, if there is a way to avoid cursor redraws, go for it.
Can you tell when does the cursor need to be redrawn on X?
> Double buffering is a port specific solution, unless the display engine does double buffering by having two sets of glyphs and compares them to see what has really changed. Sounds like a big project.
We do have 2 sets of glyphs, but they are not guaranteed to be
complete: we only care about the portions of display that changed, so
the parts that we know didn't change we don't bother updating.
next prev parent reply other threads:[~2014-02-05 3:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 1:01 bug#16621: 24.3.50; Periodic timer + overlays = flickering near point Dmitry Gutov
2014-02-02 2:33 ` Stefan Monnier
2014-02-02 2:37 ` Dmitry Gutov
2014-02-02 16:39 ` Eli Zaretskii
2014-02-03 2:12 ` Stefan Monnier
2014-02-03 5:47 ` Eli Zaretskii
2014-02-03 13:41 ` Stefan Monnier
2014-02-03 16:14 ` Eli Zaretskii
2014-02-04 3:28 ` Stefan Monnier
2014-02-04 3:44 ` Eli Zaretskii
2014-02-04 2:34 ` Dmitry Gutov
2014-02-04 3:48 ` Eli Zaretskii
2014-02-04 6:17 ` Dmitry Gutov
2014-02-04 16:00 ` Eli Zaretskii
2014-02-04 22:08 ` Jan D.
2014-02-05 3:57 ` Eli Zaretskii [this message]
2014-02-05 6:02 ` Jan Djärv
2014-02-05 15:40 ` Eli Zaretskii
2014-02-05 13:46 ` Stefan Monnier
2014-02-05 15:59 ` Eli Zaretskii
2014-02-05 18:57 ` Stefan Monnier
2014-02-05 20:00 ` Eli Zaretskii
2014-02-05 21:46 ` Stefan Monnier
2014-02-06 5:56 ` Eli Zaretskii
2014-02-06 13:08 ` Stefan Monnier
2014-02-06 14:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ppn21a9s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16621@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=jan.h.d@swipnet.se \
/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.