From: Eli Zaretskii <eliz@gnu.org>
To: pipcet@gmail.com
Cc: 41454@debbugs.gnu.org
Subject: bug#41454: 28.0.50; [".+" 0 font-shape-gstring] composition rule breaks paren highlighting
Date: Sun, 31 May 2020 21:01:44 +0300 [thread overview]
Message-ID: <83mu5oj853.fsf@gnu.org> (raw)
In-Reply-To: <83r1v0j8og.fsf@gnu.org> (message from Eli Zaretskii on Sun, 31 May 2020 20:50:07 +0300)
> Date: Sun, 31 May 2020 20:50:07 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 41454@debbugs.gnu.org
>
> The problem is that the entire sequence of characters that matches
> the regexp is passed to the shaper, and the result is stored as a
> single composition. And we have special code in the display engine
> not to break sequences of potentially-composed characters when
> handling faces (see compute_stop_pos). So I think there might be
> some bug there which shows when a composition comprises more than a
> single grapheme cluster, and some face is applied to them.
On second thought, I'm not sure this is the right place to look at.
It could be fill_gstring_glyph_string and BUILD_GSTRING_GLYPH_STRING
instead (and the respective *term.c display functions).
next prev parent reply other threads:[~2020-05-31 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 12:50 bug#41454: 28.0.50; [".+" 0 font-shape-gstring] composition rule breaks paren highlighting Pip Cet
2020-05-22 13:01 ` Eli Zaretskii
2020-05-22 13:18 ` Pip Cet
2020-05-22 13:23 ` Eli Zaretskii
2020-05-31 17:50 ` Eli Zaretskii
2020-05-31 18:01 ` Eli Zaretskii [this message]
2020-05-31 19:58 ` Pip Cet
2020-06-01 16:17 ` Eli Zaretskii
2020-06-03 7:50 ` Pip Cet
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=83mu5oj853.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41454@debbugs.gnu.org \
--cc=pipcet@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).