bug#16368: [PATCH] cperl-mode: don't freeze over a cool regexp

From	Stefan Kangas <stefankangas@gmail.com>
Newsgroups	gnu.emacs.bug
Subject	bug#16368: [PATCH] cperl-mode: don't freeze over a cool regexp
Date	2020-09-03 02:58 -0700
Message-ID	<mailman.2174.1599127145.2469.bug-gnu-emacs@gnu.org> (permalink)
References	<87iotxq4oy.fsf@xvii.vinc17.org> <e77e2af2-54fd-042a-7f91-cdbe013d1eb2@posteo.de> <CADwFkmm=7txZFvs8Ozg0y181DCbUUreV8ojhuQC6xpDw5ssjDQ@mail.gmail.com> <1dce9689-f0ae-e066-bbf0-fb92f9b997ce@posteo.de> <CADwFkmmsYYPZgibTWSPJVRLkvce3tdK-HO42BWiBDZMqc6OkrQ@mail.gmail.com>

Show all headers | View raw

Harald Jörg <haj@posteo.de> writes:

> I'd say this is desired behavior.

OK, thanks.  Your explanation sounds good to me.

> I can only guess that the first part of the message (which starts with
> "cperl-forward-group-in-re") was added out of frustration: The bug
> prevented the second part of the message (without
> "cperl-forward-group-in-re") from ever appearing.  Only this wasn't
> fatal unless... there was this closing brace two characters before.
> I'll check that, and prepare an updated patch if that's true.

Sounds good.

> No problem, I'll do so.  I thought I was supposed to create the commit
> messages with C-x 4 a, but probably I misunderstood and should have
> post-processed that text in the first place.

I always use C-x 4 a, and then delete the spacing to the left.

> Hm. That should rather be _moving_ that line to the top?

Ah, right.  Yup, that sounds good.

Back to gnu.emacs.bug | Previous | Next | Find similar

Thread

bug#16368: [PATCH] cperl-mode: don't freeze over a cool regexp Stefan Kangas <stefankangas@gmail.com> - 2020-09-03 02:58 -0700

csiph-web