From: Dmitry Gutov <dmitry@gutov.dev>
To: Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
67262@debbugs.gnu.org, JD Smith <jdtsmith@gmail.com>
Subject: bug#67262: python-ts-mode cannot identify triple-quoted-strings
Date: Sun, 24 Dec 2023 02:45:25 +0200 [thread overview]
Message-ID: <2d6c8f44-e59e-4752-811a-ce7eebd3ee09@gutov.dev> (raw)
In-Reply-To: <90B31D18-7607-4D37-A6B4-5CFE3C4F40A9@gmail.com>
On 24/12/2023 01:51, Yuan Fu wrote:
> Something like this? IMHO the code is easier to understand without the syntax-propertize-rules.
Sure, fine with me.
> + (while (search-forward "\"\"\"" end t)+ (put-text-property (1- start) start
I think we also should support the triple-single-quotes, like
python-syntax-propertize-function does.
> + 'syntax-table (string-to-syntax "| "))
> + (put-text-property end (min (1+ end) (point-max))
> + 'syntax-table (string-to-syntax "| "))))))))
The spaces after "|" seem unnecessary.
next prev parent reply other threads:[~2023-12-24 0:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 15:52 bug#67262: python-ts-mode cannot identify triple-quoted-strings JD Smith
2023-11-18 16:29 ` Eli Zaretskii
2023-11-18 17:18 ` JD Smith
2023-11-18 22:52 ` Dmitry Gutov
2023-11-25 10:01 ` Eli Zaretskii
2023-11-25 14:42 ` JD Smith
2023-11-26 2:04 ` Dmitry Gutov
2023-11-26 14:58 ` Dmitry Gutov
2023-11-26 23:43 ` Yuan Fu
2023-11-27 0:05 ` Dmitry Gutov
2023-12-12 8:32 ` Yuan Fu
2023-12-12 21:55 ` Dmitry Gutov
2023-12-16 12:47 ` Eli Zaretskii
2023-12-16 13:37 ` Dmitry Gutov
2023-12-16 13:59 ` Eli Zaretskii
2023-12-16 15:11 ` JD Smith
2023-12-16 15:21 ` Dmitry Gutov
2023-12-16 15:57 ` Eli Zaretskii
2023-12-16 23:36 ` Yuan Fu
2023-12-17 13:46 ` Dmitry Gutov
2023-12-23 9:52 ` Eli Zaretskii
2023-12-23 18:03 ` Yuan Fu
2023-12-23 21:01 ` Dmitry Gutov
2023-12-23 23:51 ` Yuan Fu
2023-12-24 0:45 ` Dmitry Gutov [this message]
2023-12-24 3:10 ` Yuan Fu
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=2d6c8f44-e59e-4752-811a-ce7eebd3ee09@gutov.dev \
--to=dmitry@gutov.dev \
--cc=67262@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=jdtsmith@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).