From: Stefan Kangas <stefankangas@gmail.com>
To: "Harald Jörg" <haj@posteo.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Perl and Emacs: Developing tests for progmodes
Date: Thu, 22 Oct 2020 12:38:04 -0700 [thread overview]
Message-ID: <CADwFkm=dEL5yofc0dt38amVQe-OA3YnzJvj7v7v_U-3p-Z7WAA@mail.gmail.com> (raw)
In-Reply-To: <87sga69qa0.fsf@hajtower>
haj@posteo.de (Harald Jörg) writes:
> Stefan (Monnier) already committed this as a patch (7a7847d7ad5;
> Fri Aug 14) :)
I was referring to my separate patch, now committed in 754a2f11b8.
Sorry for being unclear.
> My recent addition to the tests (fb26dc13: cperl-mode: Delete a
> misleading comment, add tests for verification; Mon Oct 19) shows
> another issue: The test (fontification of \$") makes sense for both
> cperl-mode and perl-mode. In cperl-mode, the fontification was fixed in
> 1997 (I think), in perl-mode it is still wrong. I'm not deep enough in
> either of the modes (yet) to figure out what to do to fix this in
> perl-mode, so I decided to only run the test for cperl-mode.
>
> Finally, perl-mode comes with its own list of ancient open bugs, many of
> those don't occur in cperl-mode. I wonder whether the authors of these
> bugs would accept "use cperl-mode instead" as a workaround?
>
> At some time, it might make sense to merge those two modes into one.
> Perl continues to evolve, and upgrading two modes to support that
> doesn't seem to be an economic use of time.
Some interesting points. I'm interested to hear what others have to
say about them.
next prev parent reply other threads:[~2020-10-22 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:42 Perl and Emacs: Developing tests for progmodes Harald Jörg
2020-09-03 15:52 ` Stefan Monnier
2020-09-03 20:17 ` Stefan Kangas
2020-10-22 13:42 ` Stefan Kangas
2020-10-22 15:28 ` Stefan Monnier
2020-10-22 16:32 ` Stefan Kangas
2020-10-22 16:30 ` Harald Jörg
2020-10-22 19:38 ` Stefan Kangas [this message]
2020-09-03 17:34 ` Eli Zaretskii
2020-09-03 20:00 ` Harald Jörg
2020-09-04 6:55 ` Eli Zaretskii
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='CADwFkm=dEL5yofc0dt38amVQe-OA3YnzJvj7v7v_U-3p-Z7WAA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@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).