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: Mon, 29 Apr 2024 18:34:40 +0300	[thread overview]
Message-ID: <86o79sqj1r.fsf@gnu.org> (raw)
In-Reply-To: <BF753F9C-6DF4-4302-9EB6-3F05467BD54D@gmail.com> (message from JD Smith on Mon, 29 Apr 2024 11:19:52 -0400)

> From: JD Smith <jdtsmith@gmail.com>
> Date: Mon, 29 Apr 2024 11:19:52 -0400
> Cc: 70637@debbugs.gnu.org
> 
>  This happens when the glyph under cursor has the beginning-of-box or
>  end-of-box flag set.  When we display the entire stretch of characters
>  on that line, we (correctly) don't pay attention to these flags in the
>  middle of the glyph sequence, but redrawing the cursor draws just one
>  glyph, and knows nothing about those before or after it.  So it draws
>  the unnecessary border, because the glyph under cursor has the flag
>  set.
> 
>  Those box flags are set on the glyphs produced from the display
>  strings because when we process the beginning or end of the string, we
>  don't have any idea whether the characters of the underlying buffer
>  text before/after the string have the same value of the :box face, so
>  we cannot avoid setting these flags at the first and the last
>  character of the display string.
> 
>  
> I see, makes sense.  So the cursor blink code would also have to "look ahead/behind" the underlying glyph to
> know whether to ignore the flag.

It's not just to "look", it's actually to redraw.  because the logic
which determines whether we draw the borders lives in the code that
draws the glyphs on the glass, and to DTRT it needs to be presented
with a sequence of glyphs that begins before the one under cursor and
ends after it.

> Probably this is such a rare case that unless there are other related
> artifacts, it's worth documenting but not fixing.

Suggestions for how to document this are welcome.





  reply	other threads:[~2024-04-29 15:34 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 [this message]
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=86o79sqj1r.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).