From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36472@debbugs.gnu.org
Subject: bug#36472: 27.0.50; Convey information by showing line numbers using different colors?
Date: Tue, 2 Jul 2019 18:49:38 +0300 [thread overview]
Message-ID: <761edfce-9f36-8570-3700-a8bb5ced99b0@yandex.ru> (raw)
In-Reply-To: <835zoke9at.fsf@gnu.org>
On 02.07.2019 18:38, Eli Zaretskii wrote:
> I don't understand: who would need to look up overlays? And how will
> "it" know that it needs to look up overlays?
The function that diff-hl would add to the said hook. So it will know.
> IOW, I don't think I understand the API you had in mind. You
> originally said "a hook", which implies the display engine would call
> a hook variable, but now it sounds like you had something else in
> mind.
Something like:
(defvar display-line-number-renderers-functions nil
"The line number (a string) is mapped through all of the functions in
this list, in turn. Each receives it as an argument, and then the return
value is used. The functions are called in the buffer for which the line
numbers are displayed, at the beginning of a line which corresponds to
the given number.")
(add-hook 'display-line-number-renderers 'diff-hl-line-number-renderer)
(defun diff-hl-line-number-renderer (line-number-string)
(cl-case (get-text-property (point) 'diff-hl-indicator-type)
...)
next prev parent reply other threads:[~2019-07-02 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 11:14 bug#36472: 27.0.50; Convey information by showing line numbers using different colors? Dmitry Gutov
2019-07-02 14:30 ` Eli Zaretskii
2019-07-02 15:09 ` Dmitry Gutov
2019-07-02 15:38 ` Eli Zaretskii
2019-07-02 15:49 ` Dmitry Gutov [this message]
2019-07-02 16:27 ` Eli Zaretskii
2019-07-03 14:19 ` Dmitry Gutov
2019-07-03 16:14 ` Eli Zaretskii
2019-07-07 23:46 ` Dmitry Gutov
2019-07-08 12:23 ` Eli Zaretskii
2019-07-15 15:16 ` Dmitry Gutov
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=761edfce-9f36-8570-3700-a8bb5ced99b0@yandex.ru \
--to=dgutov@yandex.ru \
--cc=36472@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.