unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: Peter Oliver <p.d.oliver@mavit.org.uk>, emacs-devel@gnu.org
Subject: Re: Does Emacs need two Perl modes?
Date: Sun, 18 Jun 2023 14:56:38 +0200	[thread overview]
Message-ID: <4d18a051-07d5-fba7-1c36-ae2eb72bf71c@vodafonemail.de> (raw)
In-Reply-To: <16da6ae7-66d8-fc43-cb84-6d104d3a2ef8@mavit.org.uk>

On 2023-06-18  12:14, Peter Oliver wrote:

> Does it still make sense for Emacs to include two different Perl modes?  
> Is it time to make cperl-mode the default, and to deprecate perl-mode?

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'.

Why not leave `perl-mode' in self-maintenance mode as long as users are 
happy with it?

I won't say "no" when we talk about giving `cperl-mode' preference in 
`auto-mode-alist', though.



  parent reply	other threads:[~2023-06-18 12:56 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 [this message]
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   ` Does Emacs need two Perl modes? Richard Stallman

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=4d18a051-07d5-fba7-1c36-ae2eb72bf71c@vodafonemail.de \
    --to=jschmidt4gnu@vodafonemail.de \
    --cc=emacs-devel@gnu.org \
    --cc=p.d.oliver@mavit.org.uk \
    /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).