all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Harald Jörg" <haj@posteo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Re-vitalizing cperl-mode
Date: Thu, 02 Jul 2020 09:40:14 -0400	[thread overview]
Message-ID: <jwv8sg2vyhz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <7e274cb1-dfeb-6d04-0ffc-892f55eba659@posteo.de> ("Harald Jörg"'s message of "Thu, 2 Jul 2020 13:34:43 +0200")

Hi,

> Emacs comes with cperl-mode, a major mode to edit Perl programs.

As well as `perl-mode`, indeed.

> However, Perl is evolving... and I noticed that cperl-mode isn't
> developed accordingly.

Indeed, neither `perl-mode` nor `cperl-mode` are getting much love
these days.

> Should I just keep the status quo - and the Emacs dev team will decide
> whether, and which of my changes you will adopt into the next Emacs
> release?

Much better would be for you to step up as maintainer of the package:
it's likely that in many cases the "Emacs dev team" wouldn't really have
the resources or expertise to judge such changes.

We can give guidance and feedback on the quality of the Elisp code, of
course.

> Would it be an option to give cperl-mode a "dual life" in Emacs and in
> (M)ELPA?

Yes, we could easily distribute emacs.git's ` cperl-mode.el` as a GNU
ELPA package as well (like we already do for python.el and a bunch of
others).

> In any case: What rules / conventions / tools and frameworks should I
> obey to make my changes palatable for Emacs and/or (M)ELPA?

Since `cperl-mode.el` is distributed with Emacs, its better to try and
obey the conventions used for Emacs's own Elisp code.

Adding test cases under emacs.git/test would be a great contribution
as well (there's currently a very limited set of testcases in
test/manual/indent/perl.perl).

The main rule there is that code's copyright needs to be assigned to
the FSF.  I'll contact you off-list for that.


        Stefan


PS: BTW, I assume you're familiar with https://github.com/jrockway/cperl-mode?




  parent reply	other threads:[~2020-07-02 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 11:34 Re-vitalizing cperl-mode Harald Jörg
2020-07-02 13:26 ` Eli Zaretskii
2020-07-02 14:28   ` Harald Jörg
2020-07-02 13:40 ` Stefan Monnier [this message]
2020-07-02 14:56   ` Harald Jörg

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=jwv8sg2vyhz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=haj@posteo.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 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.