From: Richard Stallman <rms@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: emacs-devel@gnu.org
Subject: Re: Does Emacs need two Perl modes?
Date: Mon, 19 Jun 2023 22:57:10 -0400 [thread overview]
Message-ID: <E1qBRYM-0004MW-RW@fencepost.gnu.org> (raw)
In-Reply-To: <4d18a051-07d5-fba7-1c36-ae2eb72bf71c@vodafonemail.de> (message from Jens Schmidt on Sun, 18 Jun 2023 14:56:38 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> But then there are those, like me, who tried `cperl-mode', found it too
> (shamlessly generalizing here) electric, dwimmy, flashy, whatever, and
> who ruefully returned to `perl-mode', not wanting to invest any time to
> de-electrify, de-dwim, de-flash `cperl-mode'.
Nobody has an obligation to do it. Nonetheless, the Emacs developers
still do have the option of doing it.
Adding options to Cperl mode that will make it as convenient as Perl
mode (or perhaps even more so) for users like you may be less work in
the long run than maintaining Perl mode as well.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2023-06-20 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 10:14 Does Emacs need two Perl modes? Peter Oliver
2023-06-18 12:15 ` Po Lu
2023-06-18 12:56 ` Jens Schmidt
2023-06-19 13:01 ` Corwin Brust
2023-06-19 14:34 ` Enhancing cperl-mode (was: Re: Does Emacs need two Perl modes?) Harald Jörg
2023-06-19 14:58 ` Corwin Brust
2023-06-19 16:41 ` Enhancing cperl-mode Harald Jörg
2023-06-19 21:49 ` Corwin Brust
2023-06-20 2:57 ` Richard Stallman [this message]
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=E1qBRYM-0004MW-RW@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jschmidt4gnu@vodafonemail.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).