From: Dmitry Gutov <dgutov@yandex.ru>
To: kobarity <kobarity@gmail.com>, Ruijie Yu <ruijie@netyu.xyz>
Cc: Rob Moss <robm.dev@gmail.com>, Lele Gaifax <lele@metapensiero.it>,
62031@debbugs.gnu.org
Subject: bug#62031: 29.0.60; python-mode indentation after re.match
Date: Thu, 9 Mar 2023 17:42:32 +0200 [thread overview]
Message-ID: <ebdb437a-eae9-f96f-660e-ed38e4537311@yandex.ru> (raw)
In-Reply-To: <eke7mt4mvt88.wl-kobarity@gmail.com>
On 09/03/2023 17:29, kobarity wrote:
> Ruijie Yu wrote:
>> As I mentioned in the other subthread, there is a variation to this
>> issue that remains unfixed. The following test case, a slightly
>> modified version of the test case in your commit, has failed (tested on
>> 7e1012765c40):
> I think it's better to check the block-start is located at the
> beginning of the line. Attached is a patch which can pass the test
> case.
Thank you, I've pushed a different patch which checks for the same thing.
This is consistent with the search in python-nav-forward-block, for
example. So it seems correct.
next prev parent reply other threads:[~2023-03-09 15:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:44 bug#62031: 29.0.60; python-mode indentation after re.match Rob Moss
2023-03-07 14:35 ` Dmitry Gutov
2023-03-07 14:57 ` Lele Gaifax
2023-03-07 23:31 ` Rob Moss
2023-03-08 7:53 ` Lele Gaifax
2023-03-08 13:23 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 22:46 ` Dmitry Gutov
2023-03-09 2:31 ` Rob Moss
2023-03-08 13:54 ` Eli Zaretskii
2023-03-08 17:57 ` Dmitry Gutov
2023-03-08 18:10 ` Lele Gaifax
2023-03-08 20:52 ` Dmitry Gutov
2023-03-09 3:04 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-09 15:29 ` kobarity
2023-03-09 15:42 ` Dmitry Gutov [this message]
2023-03-09 15:44 ` Lele Gaifax
2023-03-09 15:40 ` Dmitry Gutov
2023-03-08 18:15 ` Dmitry Gutov
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=ebdb437a-eae9-f96f-660e-ed38e4537311@yandex.ru \
--to=dgutov@yandex.ru \
--cc=62031@debbugs.gnu.org \
--cc=kobarity@gmail.com \
--cc=lele@metapensiero.it \
--cc=robm.dev@gmail.com \
--cc=ruijie@netyu.xyz \
/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.