From: "João Távora" <joaotavora@gmail.com>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: Eason Huang <aqua0210@foxmail.com>, 60087@debbugs.gnu.org
Subject: bug#60087: 29.0.60; c++-ts-mode conflict with electric-pair-mode
Date: Thu, 15 Dec 2022 13:10:00 +0000 [thread overview]
Message-ID: <CALDnm5299RKwmn=SXW61p55zbd+Y4DJBLZwisJ59Z2HEVt7jNA@mail.gmail.com> (raw)
In-Reply-To: <m1a63oyhw2.fsf@yahoo.es>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Thu, Dec 15, 2022 at 12:25 PM Daniel Martín via Bug reports for GNU
Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org> wrote:
>
> Thanks for the report. I think the bug is that we need a second
> character in the syntax table entry, to set the correct matching
> delimiter.
>
> Does the following patch solve this issue and bug#60049?
>
>
I don't know how this can work if '<' is going to be used to input
the less-than operator. I think more complex syntax-propertization
functionality is going to be needed here. I don't have a tree-sitter
build to test, but I'd say that the tree-sitter backend should be asked
about what kind of '<' and '>' we're talking about. AFAICT, just
saying that '<' has the delimiter syntax in C++ is wrong. It's not
like '(' or '{.'
João
[-- Attachment #2: Type: text/html, Size: 1265 bytes --]
next prev parent reply other threads:[~2022-12-15 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 11:17 bug#60087: 29.0.60; c++-ts-mode conflict with electric-pair-mode Eason Huang
2022-12-15 12:24 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-15 13:10 ` João Távora [this message]
2022-12-15 21:34 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-15 21:43 ` João Távora
2022-12-27 9:03 ` Eason Huang
2022-12-29 6:10 ` Eason Huang
2022-12-29 6:33 ` Eli Zaretskii
2022-12-29 8:43 ` Yuan Fu
2022-12-29 9:07 ` João Távora
2022-12-15 13:05 ` João Távora
2022-12-15 13:21 ` Eason Huang
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='CALDnm5299RKwmn=SXW61p55zbd+Y4DJBLZwisJ59Z2HEVt7jNA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=60087@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=mardani29@yahoo.es \
/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.