unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 11 May 2024 12:41:52 +0300	[thread overview]
Message-ID: <86cyps3ctb.fsf@gnu.org> (raw)
In-Reply-To: <E38688B6-F36C-4285-93DA-D861FB6EBB11@gmail.com> (message from JD Smith on Thu, 9 May 2024 09:31:28 -0400)

> From: JD Smith <jdtsmith@gmail.com>
> Date: Thu, 9 May 2024 09:31:28 -0400
> Cc: 70637@debbugs.gnu.org
> 
> I presume this is a more general issue than just :box.  One idea is to add a warning to the Elisp section "Display
> Specs That Replace The Text", perhaps at the end:
> 
>  Note: certain `face' attributes such as `:box' can lead to display artifacts when applied to the replacing
>  text in a `display' specification.  These attributes may be incorrectly merged with adjacent non-`display'
>  `face' properties.  This can be mitigated by applying the `face' attributes directly to the text being
>  replaced, rather than (or in addition to) the `display' replacement text itself.

Actually, this is specific to :box, since only for that attribute we
need to determine the beginning and the end of the box.

> Maybe a bit too wordy.

Yes, I agree.  If you can reword it to be specific to :box and to
include an example, I think it would be good.

Thanks.





  reply	other threads:[~2024-05-11  9:41 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
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 [this message]
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=86cyps3ctb.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).