unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Paul W. Rankin" via "Emacs development discussions." <emacs-devel@gnu.org>
To: "Harald Jörg" <haj@posteo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Please do not deprecate perl-mode in favour of cperl-mode
Date: Fri, 29 Dec 2023 13:48:46 +1000	[thread overview]
Message-ID: <44a349d973c83c3c0d71d0dbf57dfb58@purelymail.com> (raw)
In-Reply-To: <87a5qrzjej.fsf@oook.m.uunet.de>

Very sorry I seem to have lost track of the thread and some issues I 
raised you've already addressed here.

On 2023-12-03 20:10, Harald Jörg wrote:
> A better description would be: deprecate perl-mode.el in favour of
> cperl-mode.el.  It is not intended to make M-x perl-mode go away, but 
> to
> implement its look and feel with cperl-mode.el.
> 
> The main motivation for this that maintaining two modes to keep up with
> changes in Perl syntax is not very efficient.

Awesome.

> This is exactly why comments like yours are welcome: I want to know
> which of the differences are annoying for users of Perl mode.
> 
> In particular:
> 
>  - Code indentation: Both Perl mode and CPerl mode offer several user
>    options to affect indentation (too many of them in CPerl mode IMHO).
>    I am confident that it is possible to mimick Perl mode's default
>    indentation by options.  Concrete examples are very welcome (like
>    those you provided with your next reply).  They will make it into 
> the
>    test suite.
> 
>  - TAB for indenting region: That's also something that should be
>    doable.  CPerl mode's behaviour for indent-region is indeed very
>    idiosyncratic (and underdocumented).
> 
>  - use of specific faces: This will be fixed in CPerl mode anyway,
>    independent of the deprecation.  This doesn't mean that the rich
>    coloration which some people like will go away, but that all faces
>    will default to font-lock-* faces if cperl-mode.el starts in Perl
>    mode style.

Sounds wonderful :) I can't wait to discover the additions of CPerl 
Mode.



      reply	other threads:[~2023-12-29  3:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03  6:36 Please do not deprecate perl-mode in favour of cperl-mode Paul W. Rankin via Emacs development discussions.
2023-12-03  7:07 ` 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. [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=44a349d973c83c3c0d71d0dbf57dfb58@purelymail.com \
    --to=emacs-devel@gnu.org \
    --cc=haj@posteo.de \
    --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).