From: Jens Schmidt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 66050@debbugs.gnu.org, "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 18:34:46 +0200 [thread overview]
Message-ID: <87il88vjvd.fsf@sappc2.fritz.box> (raw)
In-Reply-To: <CADwFkm=2QseuH91ZBP0tCiitHYy_cVjWJCm6KLDnib_+anSkDg@mail.gmail.com> (Stefan Kangas's message of "Sun, 17 Sep 2023 05:47:49 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> 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.
There has been a thread on emacs-devel recently on that:
https://yhetil.org/emacs-devel/16da6ae7-66d8-fc43-cb84-6d104d3a2ef8@mavit.org.uk/
plus my opinion:
https://yhetil.org/emacs-devel/4d18a051-07d5-fba7-1c36-ae2eb72bf71c@vodafonemail.de/
which still holds.
But I can see your points, of course.
cperl-mode already has some big-config-sweep-knobs, like it seems
(`cperl-hairy'). It would certainly be nice to also have some
"make-things-work-like-in-perl-mode-but-sans-its-bugs" knob if it came
to obsoleting perl-mode. For me, the most important things to cover
here would be a nearly-identical look-and-feel for indentation and
syntax highlighting.
One could even imagine to flip that knob automatically when `cperl-mode'
gets started as `perl-mode'.
> - 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.
+1, with the same restrictions on indentation and syntax highlighting.
After 25+ years of using one mode you just get so used to its
look-and-feel.
next prev parent reply other threads:[~2023-09-17 16:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 12:47 bug#66050: Making perl-mode.el obsolete Stefan Kangas
2023-09-17 16:34 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il88vjvd.fsf@sappc2.fritz.box \
--to=bug-gnu-emacs@gnu.org \
--cc=66050@debbugs.gnu.org \
--cc=haj@posteo.de \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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.