From: Eli Zaretskii <eliz@gnu.org>
To: Nick Urbanik <nicku@nicku.org>
Cc: 62794-done@debbugs.gnu.org
Subject: bug#62794: 28.2; jit-lock-function enters busy loop when open """ near top of large Python program
Date: Fri, 14 Apr 2023 09:51:59 +0300 [thread overview]
Message-ID: <83y1mvez1s.fsf@gnu.org> (raw)
In-Reply-To: <ZDjsk9OoKi/FE71O@nicku.org> (message from Nick Urbanik on Fri, 14 Apr 2023 16:02:59 +1000)
> Date: Fri, 14 Apr 2023 16:02:59 +1000
> From: Nick Urbanik <nicku@nicku.org>
> Cc: 62794@debbugs.gnu.org
>
> On 13/04/23 09:01 +0300, Eli Zaretskii wrote:
> >Is it easier for you to try the pretest tarball? If so, you can find
> >the pretest here:
> >
> > https://alpha.gnu.org/gnu/emacs/pretest/emacs-29.0.90.tar.xz
>
> Thank you very much, Eli. I successfully built an RPM under mock that
> runs on Fedora 37 and am now free of that bug, and another that
> prevented the formatting of docstrings. Great, my faith in emacs is
> restored, and I can continue to be productive with it. My spec file
> is here: https://nicku.org/software/#emacs-29.0
>
> I pity all the other people stuck with 28.2 who work with Python and
> who are plagued by this barrier to getting things done.
Thanks for testing, I'm therefore closing this bug.
next prev parent reply other threads:[~2023-04-14 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 7:05 bug#62794: 28.2; jit-lock-function enters busy loop when open """ near top of large Python program Nick Urbanik
2023-04-12 15:39 ` Eli Zaretskii
2023-04-12 23:55 ` Nick Urbanik
2023-04-13 4:58 ` Eli Zaretskii
2023-04-13 5:25 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-13 5:39 ` Nick Urbanik
2023-04-13 6:01 ` Eli Zaretskii
2023-04-14 6:02 ` Nick Urbanik
2023-04-14 6:51 ` Eli Zaretskii [this message]
2023-04-14 2:49 ` Jim Porter
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=83y1mvez1s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62794-done@debbugs.gnu.org \
--cc=nicku@nicku.org \
/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.