From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23510@debbugs.gnu.org, angelo.graziosi@libero.it
Subject: bug#23510: Strange redisplay in global highlighted mode moving the scroll bar
Date: Wed, 11 May 2016 12:44:43 +0300 [thread overview]
Message-ID: <83lh3hapys.fsf@gnu.org> (raw)
In-Reply-To: <8760ul9caj.fsf@gmx.net> (message from Stephen Berman on Wed, 11 May 2016 11:25:24 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: "angelo.graziosi\@libero.it" <angelo.graziosi@libero.it>, 23510@debbugs.gnu.org
> Date: Wed, 11 May 2016 11:25:24 +0200
>
> What you say about the use of pre- and post-command-hook and moving
> overlays may well be (perhaps the main) part of the problem here, but I
> found out that there's an specific condition inducing it: I noticed that
> the flickering only happens when global-hl-line-mode is enabled, but not
> when hl-line-mode is enabled, and it turns out that the crucial
> difference between them is that in the former,
> global-hl-line-sticky-flag is nil by default, while in the latter,
> hl-line-sticky-flag is t by default: when I set
> global-hl-line-sticky-flag to t and then enable global-hl-line-mode, the
> flickering no longer happens, and when I set hl-line-sticky-flag to nil
> and then enable hl-line-mode, the flickering does happen.
If you can suggest a patch that fixes that and doesn't have any
adverse effects, please do.
next prev parent reply other threads:[~2016-05-11 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 19:31 bug#23510: Strange redisplay in global highlighted mode moving the scroll bar angelo.graziosi
2016-05-11 8:13 ` Eli Zaretskii
2016-05-11 9:25 ` Stephen Berman
2016-05-11 9:44 ` Eli Zaretskii [this message]
2016-05-12 20:41 ` Stephen Berman
2016-05-12 20:41 ` Stephen Berman
2016-05-13 17:20 ` Stephen Berman
2016-05-13 17:52 ` Stephen Berman
2016-05-14 7:42 ` Angelo Graziosi
2016-05-16 21:33 ` Stephen Berman
2016-05-16 22:28 ` Angelo Graziosi
2016-05-25 22:13 ` Angelo Graziosi
2016-05-26 2:44 ` Eli Zaretskii
2016-05-26 9:34 ` Stephen Berman
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=83lh3hapys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23510@debbugs.gnu.org \
--cc=angelo.graziosi@libero.it \
--cc=stephen.berman@gmx.net \
/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).