From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Matthew Newton <matt@knosis.org>, 36283@debbugs.gnu.org
Subject: bug#36283: 27.0.50; hl-line-mode updates the wrong window after clone-indirect-buffer
Date: Mon, 01 Feb 2021 10:31:42 +0100 [thread overview]
Message-ID: <87eei0p20x.fsf@gnus.org> (raw)
In-Reply-To: <85ef35ec0j.fsf@gmail.com> (Noam Postavsky's message of "Thu, 04 Jul 2019 17:16:28 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> Matthew Newton <matt@knosis.org> writes:
>
>> In GUI Emacs on MacOS:
>>
>> emacs -Q
>> M-x hl-line-mode
>> C-p
>> M-x clone-indirect-buffer
>> C-p
>>
>> The highlighted line moves in the inactive window and does not move
>> in the active window.
>>
>> I tested this on Emacs 24.5 from https://emacsformacosx.com/ so it
>> doesn’t appear to be recent or specific to my build.
>>
>> Note that if global-hl-line-mode is active, it works as expected,
>> highlighting the line in the active window.
>
> I guess hl-line-mode needs to add an entry to clone-indirect-buffer-hook
> (and clone-buffer-hook; clone-buffer seems to have the same problem)
> to handle copying of hl-line-overlay.
I'm not sure it's a bug, though? `hl-line-mode' switches on
highlighting in one specific buffer. An indirect buffer is a new
buffer, and if you want line highlighting there, you should switch it on
there, I think? Automatically switching on the mode in the indirect
buffer would be surprising, I think.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-02-01 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 18:18 bug#36283: 27.0.50; hl-line-mode updates the wrong window after clone-indirect-buffer Matthew Newton
2019-07-04 21:16 ` Noam Postavsky
2021-02-01 9:31 ` Lars Ingebrigtsen [this message]
2021-02-01 16:09 ` bug#36283: [External] : " Drew Adams
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=87eei0p20x.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36283@debbugs.gnu.org \
--cc=matt@knosis.org \
--cc=npostavs@gmail.com \
/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.