From: kobarity <kobarity@gmail.com>
To: "Jakub Ječmínek" <jecminek.k@gmail.com>
Cc: 45897@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#45897: [PATCH] 27.1; python mode font-lock confused by string concatenation
Date: Sun, 21 Jan 2024 00:41:22 +0900 [thread overview]
Message-ID: <eke7h6j86mhp.wl-kobarity@gmail.com> (raw)
In-Reply-To: <83bk9gtixd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Sat, 20 Jan 2024 19:09:50 +0900,
Eli Zaretskii wrote:
>
> > From: Jakub Ječmínek <jecminek.k@gmail.com>
> > Date: Fri, 19 Jan 2024 18:25:57 +0100
> >
> > Tags: patch
> >
> > I'm sending the patch once again with correct indentation and patch tag
> > (I'm still figuring out how the bug tracker works).
>
> Thanks.
>
> Kobarity, any comments?
Thank you for the patch. I tried it and confirmed that the example
shown by Tom Tromey is fixed.
I think ppss and line-ppss would be the same in this example. Can you
give an example of a case where ppss and line-ppss are different?
I noticed an error in the commit-msg hook when applying the patch.
CONTRIBUTE states the following:
- Lines in ChangeLog entries should preferably be not longer than 63
characters, and must not exceed 78 characters, unless they consist
of a single word of at most 140 characters; this 78/140 limit is
enforced by a commit hook.
Also, the indentation still looks wrong to me. It might be better to
attach the patch instead of pasting it into the body of the mail.
Attached is a patch to add an ERT that identifies this issue. Please
add it to your patch if you like.
[-- Attachment #2: 0001-Add-an-ERT-for-bug-45897.patch --]
[-- Type: text/plain, Size: 1172 bytes --]
From af56c8c9f6e056d84b604ffc2ab85f029a74aa17 Mon Sep 17 00:00:00 2001
From: kobarity <kobarity@gmail.com>
Date: Sun, 21 Jan 2024 00:05:04 +0900
Subject: [PATCH] Add an ERT for bug#45897
* test/lisp/progmodes/python-tests.el
(python-font-lock-string-literal-concatenation): New test.
---
test/lisp/progmodes/python-tests.el | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/test/lisp/progmodes/python-tests.el b/test/lisp/progmodes/python-tests.el
index 97ffd5fe20f..59957ff0712 100644
--- a/test/lisp/progmodes/python-tests.el
+++ b/test/lisp/progmodes/python-tests.el
@@ -660,6 +660,18 @@ python-font-lock-raw-escape-sequence
(3 . font-lock-string-face) (14)
(16 . font-lock-string-face))))
+(ert-deftest python-font-lock-string-literal-concatenation ()
+ "Test for bug#45897."
+ (python-tests-assert-faces
+ "x = \"hello\"\"\"
+y = \"confused\""
+ '((1 . font-lock-variable-name-face) (2)
+ (3 . font-lock-operator-face) (4)
+ (5 . font-lock-string-face) (14)
+ (15 . font-lock-variable-name-face) (16)
+ (17 . font-lock-operator-face) (18)
+ (19 . font-lock-string-face))))
+
\f
;;; Indentation
--
2.34.1
next prev parent reply other threads:[~2024-01-20 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 18:03 bug#45897: 27.1; python mode font-lock confused by string concatenation Tom Tromey
2024-01-19 16:01 ` Jakub Ječmínek
2024-01-19 17:25 ` bug#45897: [PATCH] " Jakub Ječmínek
2024-01-20 10:09 ` Eli Zaretskii
2024-01-20 15:41 ` kobarity [this message]
2024-01-20 23:33 ` Jakub Ječmínek
2024-01-21 7:39 ` kobarity
2024-01-27 10:06 ` Eli Zaretskii
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=eke7h6j86mhp.wl-kobarity@gmail.com \
--to=kobarity@gmail.com \
--cc=45897@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jecminek.k@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).