From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37641@debbugs.gnu.org
Subject: bug#37641: major/minor tick faces bleed into empty lines at the end of buffer
Date: Tue, 8 Oct 2019 12:47:22 +0200 [thread overview]
Message-ID: <CAAeL0STBn3rYzTvjJfCfVtieHSkJaG3tWgF-L3Bhap10a5FWow@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SSUO8uMooGWnEdmsa02KphsXQnzHCUyGf55O0iGi59UUA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
Turns out there's a difference after all. See the attached images. If you
move the
cursor past the EOB, with the beyond_zv check the line is drawn with the
line-number
face, not the line-number-current-line face. If we check with it->what !=
IT_EOB,
then the line-number-current-line face is used.
I think the right thing to do, when dealing with the "phantom line" just
past the EOB,
is to:
- Use line-number-current-line, if the cursor is there.
- Use the line-number face, and not the tick faces, if the cursor is not,
regardless
of whether this phantom line would be a tick line or not if it were used.
So there's a patch that checks for tick faces with beyond_zv, for the
current line
face with it->what, and that moves all face setting for line numbers
entirely out of
the loop.
[-- Attachment #1.2: Type: text/html, Size: 924 bytes --]
[-- Attachment #2: bug-37641.patch --]
[-- Type: application/x-patch, Size: 2277 bytes --]
[-- Attachment #3: it_eob.png --]
[-- Type: image/png, Size: 4796 bytes --]
[-- Attachment #4: beyond_zv.png --]
[-- Type: image/png, Size: 5327 bytes --]
next prev parent reply other threads:[~2019-10-08 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 1:04 bug#37641: major/minor tick faces bleed into empty lines at the end of buffer Juanma Barranquero
2019-10-07 3:42 ` Juanma Barranquero
2019-10-07 16:17 ` Eli Zaretskii
2019-10-08 2:38 ` Juanma Barranquero
2019-10-08 4:23 ` Juanma Barranquero
2019-10-08 8:51 ` Eli Zaretskii
2019-10-08 8:49 ` Eli Zaretskii
2019-10-08 9:37 ` Juanma Barranquero
2019-10-08 10:47 ` Juanma Barranquero [this message]
2019-10-09 10:22 ` Eli Zaretskii
2019-10-09 10:39 ` Juanma Barranquero
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=CAAeL0STBn3rYzTvjJfCfVtieHSkJaG3tWgF-L3Bhap10a5FWow@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=37641@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 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).