From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23510@debbugs.gnu.org
Subject: bug#23510: Strange redisplay in global highlighted mode moving the scroll bar
Date: Tue, 17 May 2016 00:28:57 +0200 [thread overview]
Message-ID: <d1760ab1-2e6f-50c8-5434-2c41e1d069aa@alice.it> (raw)
In-Reply-To: <87shxhbsdu.fsf@gmx.net>
Stephen,
I tried your patch without an init file and calling "M-x hl-line-mode"
and then "M-x global-hl-line-mode" and I think I can reproduce all your
arguments below.
Now my init file contains
(setq global-hl-line-sticky-flag t)
(global-hl-line-mode 1)
so that I can see the line in all windows of the frame.
Obviously, no flickering in all case you describe below..
Angelo
Il 16/05/2016 23:33, Stephen Berman ha scritto:
> On Sat, 14 May 2016 09:42:13 +0200 Angelo Graziosi <angelo.graziosi@alice.it> wrote:
>
>>> If my fix is found acceptable
>>
>> I have tested the patch with this init.el file:
>>
>> ;;
>> (global-hl-line-mode 1)
>>
>>
>> and it seems to work..
>
> I take it you mean you see no flickering? That would confirm the patch
> fixes problem you reported. You should also see, when you make the
> frame have two (or more) windows, that the current line of only the
> selected window is highlighted; this is the default behavior without the
> patch and should obtain with the patch as well.
>
>> Any other configuration for testing?
>
> The default for global-hl-line-mode, which you tested with the above, is
> for the value of global-hl-line-sticky-flag to be nil; if you set it to
> non-nil, then when you make the frame display two (or more) windows, the
> current line is highlighted in all of them. A difference between the
> behavior of the existing version of hl-line.el and the behavior with my
> patch is that, in the former, the current line of each window displaying
> a different buffer becomes highlighted only as soon as that window is
> selected (and remains highlighted when another window is selected),
> while with my patch, the current line in all live (visible) windows is
> highlighted at once. So this is a new feature and the question is, do
> you prefer this behavior to the original behavior? (If all the windows
> display the same buffer, then with non-nil global-hl-line-sticky-flag
> the highlighting appears in all of them simultaneously both with and
> without the patch.)
>
> It would be helpful if you'd also test the behavior of the patch with
> the buffer local hl-line-mode. Here, the default is for the value of
> hl-line-sticky-flag to be non-nil, which means that if the same buffer
> is displayed in two (or more) windows of a frame, the current line is
> highlighted in each of these windows, and in addtion, when you select a
> window displaying a different buffer, the line in the previously
> selected window (displaying the buffer in which hl-line-mode was
> enabled) remains highlighted. If you set hl-line-sticky-flag to nil,
> then only the current line of the selected window is highlighted. These
> behaviors of hl-line-mode should still be the same with the patch. But
> without the patch, setting hl-line-sticky-flag to nil results in
> flickering of the highlighted line when moving the scroll bar with the
> mouse; with the patch, there should be no flickering.
>
> Steve Berman
>
next prev parent reply other threads:[~2016-05-16 22:28 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1760ab1-2e6f-50c8-5434-2c41e1d069aa@alice.it \
--to=angelo.graziosi@alice.it \
--cc=23510@debbugs.gnu.org \
--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 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.