From: Stefan Kangas <stefankangas@gmail.com>
To: "Harald Jörg" <haj@posteo.de>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: eliz@gnu.org, 66050@debbugs.gnu.org
Subject: bug#66050: Making perl-mode.el obsolete
Date: Sun, 24 Sep 2023 00:31:15 -0700 [thread overview]
Message-ID: <CADwFkmkhAJe1LvYWYdGPrPWkBaByTvRJ_JC2TTWZLUdqXbec-w@mail.gmail.com> (raw)
In-Reply-To: <87y1gw8kof.fsf@oook.m.uunet.de>
Harald Jörg <haj@posteo.de> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> I think the best option is to obsolete `perl-mode` and to encourage
>> people to report bugs against `cperl-mode` when they find it doesn't
>> work as well as their beloved `perl-mode` :-)
>
> +1
How about this basic plan:
First, we make perl-mode.el obsolete on master.
Second, we announce that people should report bugs against cperl-mode
where they want it to be more like perl-mode, and that we are looking
for interested volunteers to help work on implementing this.
Third, we close all bugs against perl-mode as wontfix, and recommend the
reporter to see if it is fixed by using cperl-mode instead.
Fourth, if we don't have enough tangible progress in cperl-mode, we can
unobsolete perl-mode.el on the Emacs 30 release branch, right after it
is cut, while keeping it in obsolete/ on master. That would give us
additional time to make sure cperl-mode.el is up to scratch.
My idea here is to motivate people to work on cperl-mode, avoid
unnecessary bikeshedding, and to take a firm stance on the direction we
want to take as a project here.
Does anyone object to or see any problems with the above?
next prev parent reply other threads:[~2023-09-24 7:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 12:47 bug#66050: Making perl-mode.el obsolete Stefan Kangas
2023-09-17 16:34 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-17 18:20 ` Stefan Kangas
2023-09-17 20:59 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 7:39 ` Stefan Kangas
2023-09-24 0:02 ` Harald Jörg
2023-09-24 15:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 21:29 ` Harald Jörg
2023-09-24 22:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 9:18 ` Harald Jörg
2023-09-25 10:09 ` Mauro Aranda
2023-09-25 10:34 ` Harald Jörg
2023-09-18 14:11 ` Corwin Brust
2023-09-20 18:34 ` Richard Stallman
2023-09-20 23:26 ` Stefan Kangas
2023-09-21 0:08 ` Corwin Brust
2023-09-21 0:16 ` Stefan Kangas
2023-09-21 0:37 ` Corwin Brust
2023-09-21 0:49 ` Stefan Kangas
2023-09-21 14:13 ` Mauro Aranda
2023-09-21 14:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 20:14 ` Mauro Aranda
2023-09-24 5:30 ` Stefan Kangas
2023-09-24 22:21 ` Harald Jörg
2023-09-24 22:40 ` Mauro Aranda
2023-09-25 8:33 ` Harald Jörg
2023-09-25 13:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 22:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 8:40 ` Harald Jörg
2023-09-18 16:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 0:44 ` Harald Jörg
2023-09-24 7:31 ` Stefan Kangas [this message]
2023-09-24 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26 9:02 ` Richard Stallman
2023-09-23 22:13 ` Harald Jörg
2023-09-24 10:41 ` Stefan Kangas
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=CADwFkmkhAJe1LvYWYdGPrPWkBaByTvRJ_JC2TTWZLUdqXbec-w@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=66050@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=haj@posteo.de \
--cc=monnier@iro.umontreal.ca \
/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).