From: "Harald Jörg" <haj@posteo.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10483@debbugs.gnu.org
Subject: bug#10483: [PATCH] cperl-mode: Avoid endless loop
Date: Mon, 31 Aug 2020 20:08:06 +0200 [thread overview]
Message-ID: <bdfd1efb-7012-0fce-9029-6499fecbf101@posteo.de> (raw)
In-Reply-To: <83o8mqwwx2.fsf@gnu.org>
On 8/31/20 7:24 PM, Eli Zaretskii wrote:
>> From: Harald Jörg <haj@posteo.de>
>> Date: Mon, 31 Aug 2020 19:06:08 +0200
>>
>> That bug has a few more manifestations. An endless loop
>> occurred whenever a statement ended in a closing paren, and
>> the statement was not terminated on the same line.
>
> Thanks, but could we please also have a test for this issue, so that
> the bug never happens again?
Sure... I can prepare another patch. The test also ought to verify
that terminating the while loop didn't damage cperl-mode's ability to
indent the compound statements it handles in this section of code.
I was hesitating in this particular case because _if_ this issue ever
happens again, then the test just hangs forever.
Is there a safeguard against this?
--
Cheers,
haj
next prev parent reply other threads:[~2020-08-31 18:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 0:02 bug#10483: 24.0.92; cperl-indent-exp hangs Eric Hanchrow
2020-08-31 17:06 ` bug#10483: [PATCH] cperl-mode: Avoid endless loop Harald Jörg
2020-08-31 17:24 ` Eli Zaretskii
2020-08-31 18:08 ` Harald Jörg [this message]
2020-08-31 18:49 ` Eli Zaretskii
2020-08-31 21:23 ` Stefan Kangas
2020-09-01 16:12 ` Harald Jörg
2020-09-04 3:17 ` Lars Ingebrigtsen
2020-09-04 7:15 ` Eli Zaretskii
2020-09-04 10:41 ` Lars Ingebrigtsen
2020-09-04 10:51 ` Andreas Schwab
2020-09-04 10:55 ` Lars Ingebrigtsen
2020-09-04 11:36 ` Eli Zaretskii
2020-09-04 12:00 ` Lars Ingebrigtsen
2020-09-04 12:05 ` Andreas Schwab
2020-09-04 11:34 ` Eli Zaretskii
2020-09-04 11:59 ` Lars Ingebrigtsen
2020-09-04 12:28 ` Eli Zaretskii
2020-09-04 12:36 ` Lars Ingebrigtsen
2020-09-04 12:09 ` Andreas Schwab
2020-10-05 18:30 ` bug#10483: [PATCH] Fix a bogus test introduced by treating (Bug#10483) Harald Jörg
2020-10-06 1:40 ` Lars Ingebrigtsen
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=bdfd1efb-7012-0fce-9029-6499fecbf101@posteo.de \
--to=haj@posteo.de \
--cc=10483@debbugs.gnu.org \
--cc=eliz@gnu.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.