From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 41454@debbugs.gnu.org
Subject: bug#41454: 28.0.50; [".+" 0 font-shape-gstring] composition rule breaks paren highlighting
Date: Fri, 22 May 2020 16:01:24 +0300 [thread overview]
Message-ID: <83h7w82kez.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBfRzwRarKQCPAYSgRvAdwycgUV9sPKs5s4YkeD0wa7nxw@mail.gmail.com> (message from Pip Cet on Fri, 22 May 2020 12:50:13 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Fri, 22 May 2020 12:50:13 +0000
>
> There seems to be a general problem using such regexps in the
> composition-function-table.
Could be, because it's a very unusual thing to do.
> If I evaluate this in emacs -Q (by placing point after it and hitting C-x C-e)
>
> (custom-set-faces
> '(default ((t (:family "Libertinus Serif" :height 330)))))
> (set-char-table-range composition-function-table t '([".+" 0
> font-shape-gstring]))
>
> the font correctly changes to a very large Libertinus font. I then hit
> C-b C-d ) and the entire last line is highlighted, not just the
> opening parenthesis. After the blink delay is over, the opening
> parenthesis and the "s" following it are unhighlighted, but the rest
> of the line is not. It stays like that permanently (screenshot
> attached).
I think this is expected, since you told Emacs all those characters
are a single grapheme cluster.
The regexps in composition-function-table should match only characters
that are supposed to be composed.
next prev parent reply other threads:[~2020-05-22 13: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 [this message]
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
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=83h7w82kez.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).