GNU bug report logs - #41454
28.0.50; [".+" 0 font-shape-gstring] composition rule breaks paren highlighting

Previous Next

Package: emacs;

Reported by: Pip Cet <pipcet <at> gmail.com>

Date: Fri, 22 May 2020 12:51:02 UTC

Severity: normal

Found in version 28.0.50

Done: Pip Cet <pipcet <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 41454 <at> debbugs.gnu.org (full text, mbox):

From: Pip Cet <pipcet <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 41454 <at> debbugs.gnu.org
Subject: Re: bug#41454: 28.0.50; [".+" 0 font-shape-gstring] composition rule
 breaks paren highlighting
Date: Fri, 22 May 2020 13:18:09 +0000
On Fri, May 22, 2020 at 1:01 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Pip Cet <pipcet <at> 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?




This bug report was last modified 4 years and 355 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.