From: Stefan Kangas <stefankangas@gmail.com>
To: 66050@debbugs.gnu.org
Cc: "Harald Jörg" <haj@posteo.de>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: bug#66050: Making perl-mode.el obsolete
Date: Sun, 17 Sep 2023 05:47:49 -0700 [thread overview]
Message-ID: <CADwFkm=2QseuH91ZBP0tCiitHYy_cVjWJCm6KLDnib_+anSkDg@mail.gmail.com> (raw)
Severity: wishist
I don't think it makes sense for us to spend our meager resources
maintaining two major modes for Perl. I would like to gauge what people
think about obsoleting perl-mode.el.
Harald Jörg wrote previously on emacs-devel:
> Finally, perl-mode comes with its own list of ancient open bugs, many of
> those don't occur in cperl-mode. I wonder whether the authors of these
> bugs would accept "use cperl-mode instead" as a workaround?
>
> At some time, it might make sense to merge those two modes into one.
> Perl continues to evolve, and upgrading two modes to support that
> doesn't seem to be an economic use of time.
https://lists.gnu.org/r/emacs-devel/2020-10/msg01492.html
Here are some additional observations:
- cperl-mode.el sees more maintenance than perl-mode.el, in large part
thanks to the efforts of Harald Jörg.
- The Perl community tends to favor cperl-mode over perl-mode.
perl-mode is seen as lacking in features compared to cperl-mode, and
no significant development has taken place to bridge the gap.
- cperl-mode.el used to be maintained outside of Emacs, but this is no
longer the case. All relevant development has been merged into and
takes place in emacs.git.
- Perl, while historically important to hacker culture and still widely
used in some quarters (e.g. Debian), is seeing much less use today
than it used to. This will negatively affect the amount of help we
can expect with maintaining these modes from others.
- Instead of maintaining perl-mode.el, I'd rather see that people worked
on a new perl-ts-mode.el. From a web search, more than one treesitter
grammar exist; I have no idea which one is the most promising or how
mature any of them are.
next reply other threads:[~2023-09-17 12:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 12:47 Stefan Kangas [this message]
2023-09-17 16:34 ` bug#66050: Making perl-mode.el obsolete Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-17 18:20 ` Stefan Kangas
2023-09-17 20:59 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 7:39 ` Stefan Kangas
2023-09-24 0:02 ` Harald Jörg
2023-09-24 15:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 21:29 ` Harald Jörg
2023-09-24 22:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 9:18 ` Harald Jörg
2023-09-25 10:09 ` Mauro Aranda
2023-09-25 10:34 ` Harald Jörg
2023-09-18 14:11 ` Corwin Brust
2023-09-20 18:34 ` Richard Stallman
2023-09-20 23:26 ` Stefan Kangas
2023-09-21 0:08 ` Corwin Brust
2023-09-21 0:16 ` Stefan Kangas
2023-09-21 0:37 ` Corwin Brust
2023-09-21 0:49 ` Stefan Kangas
2023-09-21 14:13 ` Mauro Aranda
2023-09-21 14:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 20:14 ` Mauro Aranda
2023-09-24 5:30 ` Stefan Kangas
2023-09-24 22:21 ` Harald Jörg
2023-09-24 22:40 ` Mauro Aranda
2023-09-25 8:33 ` Harald Jörg
2023-09-25 13:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 22:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 8:40 ` Harald Jörg
2023-09-18 16:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 0:44 ` Harald Jörg
2023-09-24 7:31 ` Stefan Kangas
2023-09-24 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26 9:02 ` Richard Stallman
2023-09-23 22:13 ` Harald Jörg
2023-09-24 10:41 ` 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='CADwFkm=2QseuH91ZBP0tCiitHYy_cVjWJCm6KLDnib_+anSkDg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=66050@debbugs.gnu.org \
--cc=haj@posteo.de \
--cc=monnier@iro.umontreal.ca \
/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).