From: Eli Zaretskii <eliz@gnu.org>
To: "Harald Jörg" <haj@posteo.de>
Cc: 70948@debbugs.gnu.org
Subject: bug#70948: 29.3; cperl mode hangs on comments like "#___"
Date: Thu, 16 May 2024 21:22:39 +0300 [thread overview]
Message-ID: <865xvdiplc.fsf@gnu.org> (raw)
In-Reply-To: <874jaxhfmb.fsf@oook.m.uunet.de> (message from Harald Jörg on Thu, 16 May 2024 16:43:24 +0000)
> From: Harald Jörg <haj@posteo.de>
> Cc: 70948@debbugs.gnu.org
> Date: Thu, 16 May 2024 16:43:24 +0000
>
> Eli Zaretskii writes:
>
> > Please note that, barring any unforeseen emergencies, there will be no
> > more Emacs 29.x releases. So I'm not sure the effort of making the
> > emacs-29 branch behave better in this matter is justified.
>
> I understand!
>
> My suggested course of action would be like this:
>
> 1) Make cperl-mode.el from the master branch work with older Emacsen
> (again). This needs a one-line fix.
>
> 2) Work around the inefficient rx expansion in the master branch. This
> seems to be another one-line fix in which I replace a rx sequence by
> the expansion it gets in master (explanatory comment omitted here):
>
> (defconst cperl--basic-identifier-rx
> - '(sequence (or alpha "_") (* (or word "_")))
> + '(regex "[_[:alpha:]][_[:word:]]*"))
>
> 3) Close the bug report, noting it has already been fixed in master.
> Explain that users can use cperl-mode.el from the repository as a
> drop-in replacement in Emacs 27 or newer if they are affected by the
> bug.
SGTM, thanks.
next prev parent reply other threads:[~2024-05-16 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 16:35 bug#70948: 29.3; cperl mode hangs on comments like "#___" Patrick Goldmann
2024-05-14 17:55 ` Eli Zaretskii
2024-05-14 18:20 ` Harald Jörg
2024-05-14 18:46 ` Patrick Goldmann
2024-05-14 19:38 ` Patrick Goldmann
2024-05-14 22:34 ` Harald Jörg
2024-05-15 21:54 ` Harald Jörg
2024-05-16 8:19 ` Eli Zaretskii
2024-05-16 16:43 ` Harald Jörg
2024-05-16 18:22 ` Eli Zaretskii [this message]
2024-05-16 21:00 ` Harald Jörg
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=865xvdiplc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70948@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).