From: "Paul W. Rankin" via "Emacs development discussions." <emacs-devel@gnu.org>
To: Emacs-devel@gnu.org
Subject: Please do not deprecate perl-mode in favour of cperl-mode
Date: Sun, 03 Dec 2023 16:36:10 +1000 [thread overview]
Message-ID: <5d846dd1b7a8b557073b317863bc590a@purelymail.com> (raw)
Hello,
I am writing in response to a mention I saw today on Mastodon, which
appears supported by the EtherPad, that there is plan to deprecate Perl
Mode in favour of C Perl Mode in Emacs.
If this is true can I please urge a reconsideration?
C Perl Mode has several quirks that make it behave unlike a normal Emacs
Major mode, including:
- unorthodox code indentation
- behaviour of TAB on region does not perform indent-region
- use of specific faces instead of font-lock-* faces
(Perl Mode, meanwhile, works just fine.)
I don't wish to dampen the enthusiasm of the originator of this Perl->C
Perl idea, but I would implore you to please first address C Perl Mode's
shortcoming as a 1:1 replacement for Perl Mode before the
baby/bathwater? C Perl Mode should at least work as well as Perl Mode
before deprecation is considered.
Gracious thanks,
--
Paul W. Rankin
https://www.paulwrankin.com
next reply other threads:[~2023-12-03 6:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 6:36 Paul W. Rankin via Emacs development discussions. [this message]
2023-12-03 7:07 ` Please do not deprecate perl-mode in favour of cperl-mode Eli Zaretskii
2023-12-03 8:21 ` Paul W. Rankin via Emacs development discussions.
2023-12-03 8:34 ` Eli Zaretskii
2023-12-03 8:42 ` Emanuel Berg
2023-12-03 13:20 ` Harald Jörg
2023-12-29 3:44 ` Paul W. Rankin via Emacs development discussions.
2023-12-29 9:33 ` Stefan Kangas
2023-12-29 15:07 ` Harald Jörg
2023-12-29 21:52 ` Stefan Kangas
2023-12-30 21:10 ` Harald Jörg
2023-12-30 22:50 ` Stefan Kangas
2024-01-02 17:18 ` Harald Jörg
2024-01-02 17:33 ` Stefan Kangas
2023-12-03 10:10 ` Harald Jörg
2023-12-29 3:48 ` Paul W. Rankin via Emacs development discussions.
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=5d846dd1b7a8b557073b317863bc590a@purelymail.com \
--to=emacs-devel@gnu.org \
--cc=hello@paulwrankin.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 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).