From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: 70637@debbugs.gnu.org
Subject: bug#70637: :box vertical bar artifacts at 'display boundaries
Date: Mon, 29 Apr 2024 14:40:02 +0300 [thread overview]
Message-ID: <867cggs8h9.fsf@gnu.org> (raw)
In-Reply-To: <646DB63C-1CD0-4BF4-8303-4A92B06D08DE@gmail.com> (message from JD Smith on Sun, 28 Apr 2024 20:50:31 -0400)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sun, 28 Apr 2024 20:50:31 -0400
>
>
> I have identified a display bug related to placing :box face parameters within 'display strings. Disable font-lock mode in *scratch* and evaluate:
>
> (insert "\n"
> (propertize " " 'display (propertize " " 'face '(:box t)))
> (propertize "middle" 'face '(:box t))
> (propertize " " 'display (propertize " " 'face '(:box t))))
>
> So far so good: the box is correctly merged across all three elements and wraps around them. But now move point within and across the displayed boxed text. Internal vertical divisions bars separating the 'display and normal :box regions appear.
>
> If you add a face box property to the blank flanking strings as well, this prevents the internal boundary from appearing.
How important is it to fix this use case (as opposed to using the
workaround you describe in the last sentence)? The price for fixing
it would be that we will need to redraw more than the single glyph
below the cursor when showing the cursor (which with the default
blink-cursor-mode happens twice a second), which will cause flickering
around the cursor, and I wonder whether it's justified?
next prev parent reply other threads:[~2024-04-29 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 0:50 bug#70637: :box vertical bar artifacts at 'display boundaries JD Smith
2024-04-29 11:40 ` Eli Zaretskii [this message]
2024-04-29 12:01 ` JD Smith
2024-04-29 13:12 ` Eli Zaretskii
2024-04-29 15:19 ` JD Smith
2024-04-29 15:34 ` Eli Zaretskii
2024-05-09 7:36 ` Eli Zaretskii
2024-05-09 13:31 ` JD Smith
2024-05-11 9:41 ` Eli Zaretskii
2024-05-11 17:16 ` JD Smith
2024-05-18 9:17 ` Eli Zaretskii
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=867cggs8h9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70637@debbugs.gnu.org \
--cc=jdtsmith@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).