From: Lars Ingebrigtsen <larsi@gnus.org>
To: kobarity <kobarity@gmail.com>
Cc: Augusto Stoffel <arstoffel@gmail.com>,
Dima Kogan <dima@secretsauce.net>,
56635@debbugs.gnu.org
Subject: bug#56635: 29.0.50; [PATCH] hide-show in python-mode supports ONLY function and class blocks
Date: Wed, 17 Aug 2022 13:11:26 +0200 [thread overview]
Message-ID: <871qtfjfa9.fsf@gnus.org> (raw)
In-Reply-To: <87tu6bjghr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 17 Aug 2022 12:45:20 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> kobarity <kobarity@gmail.com> writes:
>
>> I fixed some issues in the Python patch. Please note that the fix for
>> #57223 (merged recently) is also needed for all ERTs to pass.
>
> Thanks; pushed to Emacs 29.
This led to test failures I didn't notice before pushing:
4 unexpected results:
FAILED python-hideshow-hide-all-2
FAILED python-hideshow-hide-block-1
FAILED python-hideshow-hide-levels-1
FAILED python-hideshow-hide-levels-2
So I've now reverted the change.
next prev parent reply other threads:[~2022-08-17 11:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 22:20 bug#56635: 29.0.50; [PATCH] hide-show in python-mode supports ONLY function and class blocks Dima Kogan
2022-07-23 7:58 ` Lars Ingebrigtsen
2022-07-23 15:51 ` kobarity
2022-07-23 20:41 ` Dima Kogan
2022-07-24 0:57 ` kobarity
2022-07-31 10:18 ` kobarity
2022-07-31 19:04 ` Dima Kogan
2022-08-07 14:37 ` kobarity
2022-08-08 15:16 ` Augusto Stoffel
2022-08-13 12:36 ` kobarity
2022-08-15 15:00 ` kobarity
2022-08-15 17:16 ` Dima Kogan
2022-08-16 2:28 ` kobarity
2022-08-17 10:45 ` Lars Ingebrigtsen
2022-08-17 11:11 ` Lars Ingebrigtsen [this message]
2022-08-17 11:32 ` kobarity
2022-08-24 0:39 ` Dima Kogan
2022-08-24 10:27 ` Lars Ingebrigtsen
2022-08-24 14:15 ` kobarity
2022-08-25 12:31 ` Lars Ingebrigtsen
2022-08-25 13:39 ` kobarity
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=871qtfjfa9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56635@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=dima@secretsauce.net \
--cc=kobarity@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).