From: Michael Heerdegen <michael_heerdegen@web.de>
To: dick <dick.r.chiang@gmail.com>
Cc: 54481@debbugs.gnu.org
Subject: bug#54481: 29.0.50; [PATCH] Rewrite hl-line
Date: Tue, 22 Mar 2022 04:13:58 +0100 [thread overview]
Message-ID: <87lex2vfux.fsf@web.de> (raw)
In-Reply-To: <877d8o8vuk.fsf@dick> (dick's message of "Sun, 20 Mar 2022 11:52:35 -0400")
dick <dick.r.chiang@gmail.com> writes:
> (defcustom hl-line-sticky-flag t
> - "Non-nil means the HL-Line mode highlight appears in all windows.
> -Otherwise Hl-Line mode will highlight only in the selected
> -window. Setting this variable takes effect the next time you use
> -the command `hl-line-mode' to turn Hl-Line mode on.
> -
> -This variable has no effect in Global Highlight Line mode.
> -For that, use `global-hl-line-sticky-flag'."
> + "Non-nil to preserve highlighting overlay when focus leaves window."
> :type 'boolean
> :version "22.1"
> + :group 'hl-line
> + :set (lambda (symbol value)
> + (set-default symbol value)
> + (unless value
> + (let ((selected (window-buffer (selected-window))))
> + (dolist (buffer (buffer-list))
> + (unless (eq buffer selected)
> + (with-current-buffer buffer
> + (hl-line-unhighlight))))))))
That gives me
Debugger entered--Lisp error: (void-function hl-line-unhighlight)
(hl-line-unhighlight)
(#f(compiled-function (symbol value) #<bytecode -0xa62653aea4021f4>) hl-line-sticky-flag nil)
(custom-initialize-reset hl-line-sticky-flag (funcall #'#f(compiled-function () #<bytecode 0x1dc00016fe5d4>)))
(custom-declare-variable hl-line-sticky-flag (funcall #'#f(compiled-function () #<bytecode 0x1dc00016fe5d4>)) ...)
(byte-code ...)
(hl-line-mode nil)
Same error for (require 'hl-line).
Michael.
next prev parent reply other threads:[~2022-03-22 3:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 15:52 bug#54481: 29.0.50; [PATCH] Rewrite hl-line dick
2022-03-21 15:09 ` Lars Ingebrigtsen
2022-03-22 0:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-23 8:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-23 11:35 ` dick
2022-03-23 11:55 ` Lars Ingebrigtsen
2022-03-23 13:02 ` Eli Zaretskii
2022-03-22 3:13 ` Michael Heerdegen [this message]
2022-03-22 14:12 ` dick
2022-03-22 14:12 ` dick
2022-03-22 14:59 ` Lars Ingebrigtsen
2022-03-22 14:14 ` Lars Ingebrigtsen
2022-03-22 14:24 ` dick
2022-03-22 14:35 ` Lars Ingebrigtsen
2022-03-23 2:21 ` Michael Heerdegen
2022-03-24 3:23 ` Michael Heerdegen
2022-03-24 3:39 ` Michael Heerdegen
2022-03-24 3:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 4:42 ` Michael Heerdegen
2022-03-24 4:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 5:13 ` Michael Heerdegen
2022-03-24 5:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 3:45 ` Michael Heerdegen
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=87lex2vfux.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=54481@debbugs.gnu.org \
--cc=dick.r.chiang@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 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).