From: Yuan Fu <casouri@gmail.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 59477@debbugs.gnu.org
Subject: bug#59477: python-tests fail without tree-sitter
Date: Sat, 26 Nov 2022 14:18:37 -0800 [thread overview]
Message-ID: <FC02DCBA-26AA-41EF-A62C-B93C2FB7CF2D@gmail.com> (raw)
In-Reply-To: <207B066C-2C1F-40B3-9E13-9DFC3ABCF92F@gmail.com>
> On Nov 25, 2022, at 8:50 AM, Mattias Engdegård <mattias.engdegard@gmail.com> wrote:
>
>> But if I run this in a buffer manually I get the ending newline. I’m not sure what’s the cause of that. Bisecting give 7c5d4348330b206aff1f8e5bc4fd241d6a6dc0b5, but that commit doesn’t change anything filling-related.
>
> No idea really, but it might have something to do with the fact that the changes move the assignments
>
> (setq-local font-lock-defaults
> `(,python-font-lock-keywords
> nil nil nil nil
> (font-lock-syntactic-face-function
> . python-font-lock-syntactic-face-function)))
> (setq-local syntax-propertize-function
> python-syntax-propertize-function)
>
> so that they are executed after
>
> (when python-indent-guess-indent-offset
> (python-indent-guess-indent-offset))
>
> instead of before. `python-indent-guess-indent-offset` has the side-effect of setting syntax properties, in particular for the string terminator (triple-quote in the test).
>
> This is important, because python-fill-string (called as part of fill-paragraph in the test) assumes this having already been done and if not, str-end-pos isn't computed correctly and things take a turn for the worse after that.
>
> Stefan probably knows better how this is supposed to work, but presumably python-fill-string should take measures to ensure accurate syntax properties before doing things like
>
> (re-search-forward (rx (syntax string-delimiter)) nil t)
>
> and so on. Sorry about not being of much help here.
>
Thanks, that’s a very useful information. And I can only blame myself for breaking the tests :-)
While still unable to find the culprit. I have the following observations:
1. Setting require-final-newline to t doesn’t work
2. If I change with-temp-buffer to with-current-buffer (get-buffer-create "*test*”), the problem disappears, the newlines is not dropped
3. I edebugged fill-paragraph, the newlines in the temp buffer disappears at line 865 in fill.el, where the recursive call returns. Before (funcall function justify) returns (`function` is fill-paragraph itself), the newline still exists, but after we return to the caller at line 865, the newline disappears.
I checked for newline by hitting e and evaluating (char-before (point-max))
Yuan
next prev parent reply other threads:[~2022-11-26 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 10:13 bug#59477: python-tests fail without tree-sitter Mattias Engdegård
2022-11-23 2:40 ` Yuan Fu
2022-11-23 22:00 ` Yuan Fu
2022-11-24 6:45 ` Eli Zaretskii
2022-11-25 16:50 ` Mattias Engdegård
2022-11-26 22:18 ` Yuan Fu [this message]
2022-11-27 13:07 ` Mattias Engdegård
2022-11-30 13:41 ` Mattias Engdegård
2022-12-04 7:51 ` Yuan Fu
2022-11-27 13:16 ` Mattias Engdegård
2022-11-27 14:48 ` kobarity
2022-11-28 10:01 ` Mattias Engdegård
2022-11-28 15:18 ` kobarity
2022-11-28 19:22 ` Mattias Engdegård
2022-11-28 10:18 ` Mattias Engdegård
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=FC02DCBA-26AA-41EF-A62C-B93C2FB7CF2D@gmail.com \
--to=casouri@gmail.com \
--cc=59477@debbugs.gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).