all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 13:18:09 +0000	[thread overview]
Message-ID: <CAOqdjBdAPn67iW6ppbo3r4rvWxh78FQ5Zm+WSM2Lw5p7+AdqiQ@mail.gmail.com> (raw)
In-Reply-To: <83h7w82kez.fsf@gnu.org>

On Fri, May 22, 2020 at 1:01 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.

I also see the problem when I change the pattern to "(a)" and enter
"(a)", so it's not a problem with variable-length regexps.

> I think this is expected, since you told Emacs all those characters
> are a single grapheme cluster.

I don't think it's expected for characters to stay highlighted after
the blink delay is over.

> The regexps in composition-function-table should match only characters
> that are supposed to be composed.

So it's invalid to have a regexp for a composition not supported by
the current font?





  reply	other threads:[~2020-05-22 13:18 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOqdjBdAPn67iW6ppbo3r4rvWxh78FQ5Zm+WSM2Lw5p7+AdqiQ@mail.gmail.com \
    --to=pipcet@gmail.com \
    --cc=41454@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.