From: Jackson Ray Hamilton <jackson@jacksonrayhamilton.com>
To: Dmitry Gutov <dgutov@yandex.ru>, 36053@debbugs.gnu.org
Cc: Tijs Mallaerts <tijs.mallaerts@gmail.com>
Subject: bug#36053: 27.0.50; no matching char specified in jsx syntax table
Date: Tue, 4 Jun 2019 09:07:05 -0700 [thread overview]
Message-ID: <4913170a-f736-46be-dfd2-045a33b6ef21@jacksonrayhamilton.com> (raw)
In-Reply-To: <925400ec-853f-76b4-42d9-0ca82809cb86@yandex.ru>
Hi Tijs, Dmitry,
I pushed “Specify the matching chars for JSX open/close parenthesis” to
the Emacs master branch to hopefully resolve this issue.
Jackson
On 6/3/19 7:17 AM, Dmitry Gutov wrote:
> Jackson, could you please take a look when you have the time?
>
> On 02.06.2019 12:38, Tijs Mallaerts wrote:
>> Rainbow-delimiters-mode marks the closing angle brackets of jsx
>> syntax as mismatched because no matching chars seem to be specified
>> in the jsx syntax table.
>>
>> These are the text properties of the opening angle bracket:
>> face (rainbow-delimiters-depth-2-face)
>> font-lock-multiline t
>> fontified t
>> js-jsx-close-tag-pos 97
>> js-jsx-syntax-table (4)
>> js-jsx-tag-beg (open . 57)
>> syntax-multiline t
>> syntax-table (4)
>>
>> And these are the text properties of the closing angle bracket:
>> face (rainbow-delimiters-mismatched-face)
>> font-lock-multiline t
>> fontified t
>> js-jsx-syntax-table (5)
>> syntax-multiline t
>> syntax-table (5)
next prev parent reply other threads:[~2019-06-04 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 9:38 bug#36053: 27.0.50; no matching char specified in jsx syntax table Tijs Mallaerts
2019-06-03 14:17 ` Dmitry Gutov
2019-06-04 16:07 ` Jackson Ray Hamilton [this message]
2019-06-04 17:38 ` Eli Zaretskii
2019-06-05 1:26 ` Jackson Ray Hamilton
2019-06-05 14:11 ` Tijs Mallaerts
2019-06-05 14:13 ` Dmitry Gutov
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=4913170a-f736-46be-dfd2-045a33b6ef21@jacksonrayhamilton.com \
--to=jackson@jacksonrayhamilton.com \
--cc=36053@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=tijs.mallaerts@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 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.