From: Stefan Kangas <stefankangas@gmail.com>
To: "Harald Jörg" <haj@posteo.de>, 16368@debbugs.gnu.org
Subject: bug#16368: [PATCH] cperl-mode: don't freeze over a cool regexp
Date: Thu, 3 Sep 2020 02:58:40 -0700 [thread overview]
Message-ID: <CADwFkmmsYYPZgibTWSPJVRLkvce3tdK-HO42BWiBDZMqc6OkrQ@mail.gmail.com> (raw)
In-Reply-To: <1dce9689-f0ae-e066-bbf0-fb92f9b997ce@posteo.de>
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.
next prev parent reply other threads:[~2020-09-03 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 1:28 bug#16368: 24.3; freeze in cperl mode when editing a regexp Vincent Lefevre
2019-09-20 23:33 ` Stefan Kangas
2020-09-02 20:06 ` bug#16368: [PATCH] cperl-mode: don't freeze over a cool regexp Harald Jörg
2020-09-02 22:19 ` Stefan Kangas
2020-09-02 23:40 ` Harald Jörg
2020-09-03 9:58 ` Stefan Kangas [this message]
2020-09-03 20:27 ` Harald Jörg
2020-09-03 21:12 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmsYYPZgibTWSPJVRLkvce3tdK-HO42BWiBDZMqc6OkrQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=16368@debbugs.gnu.org \
--cc=haj@posteo.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).