From: Eli Zaretskii <eliz@gnu.org>
To: kobarity <kobarity@gmail.com>
Cc: tgbugs@gmail.com, pair@ryanb.org, jdtsmith@gmail.com,
58780-done@debbugs.gnu.org
Subject: bug#58780: python.el infinite loop in info-current-defun
Date: Thu, 09 Mar 2023 12:16:37 +0200 [thread overview]
Message-ID: <837cvq2pru.fsf@gnu.org> (raw)
In-Reply-To: <eke7o7p7wqxs.wl-kobarity@gmail.com> (message from kobarity on Sun, 05 Mar 2023 17:19:43 +0900)
> Date: Sun, 05 Mar 2023 17:19:43 +0900
> From: kobarity <kobarity@gmail.com>
>
> The attached
> 0001-Fix-searching-for-end-of-string-in-python-nav-end-of.patch is my
> proposal to fix this issue with some ERTs. `forward-sexp' (in fact
> `python-nav--lisp-forward-sexp') is added to search for the end of the
> string if the string begins with single single/double-quote (' or ").
>
> I think this 0001 patch also fixes Bug#56271. At least, it passes the
> ERT python-nav-end-of-block-2 which is introduced in Bug#56271, even
> the workaround introduced in Bug#56271 is reverted. The attached
> 0002-Revert-workaround-introduced-in-Bug-56271.patch is a patch to
> revert the workaround. If the 0001 patch is accepted, the 0002 patch
> can also be applied. But if we want to be safer, we can leave the
> workaround as it is by not applying the 0002 patch.
>
> I look forward to your comments.
There were no more comments, so I've now installed both patches on the
emacs-29 branch, and I'm boldly closing this bug.
Thanks.
prev parent reply other threads:[~2023-03-09 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:06 bug#58780: python.el infinite loop in info-current-defun JD Smith
2022-12-05 14:44 ` Ryan B
2022-12-05 14:57 ` Ryan B
2022-12-05 15:01 ` Ryan B
2022-12-05 20:32 ` Ryan B
2023-03-05 8:19 ` kobarity
2023-03-09 10:16 ` Eli Zaretskii [this message]
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=837cvq2pru.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58780-done@debbugs.gnu.org \
--cc=jdtsmith@gmail.com \
--cc=kobarity@gmail.com \
--cc=pair@ryanb.org \
--cc=tgbugs@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 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.