unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kevin Ryde <user42@zip.com.au>
Cc: 5607@debbugs.gnu.org
Subject: bug#5607: 23.1; compile error regexps for perl test scripts, mark 2
Date: Sun, 28 Feb 2016 17:10:07 +1100	[thread overview]
Message-ID: <87k2lptlfk.fsf@gnus.org> (raw)
In-Reply-To: <87635srcdp.fsf@blah.blah> (Kevin Ryde's message of "Sat, 20 Feb 2010 11:15:14 +1100")

Kevin Ryde <user42@zip.com.au> writes:

> I eventually got around to revisiting the compile error regexps I made
> for perl test scripts in my compilation-perl.el.
>
> I was misguided about the "NOK" business of the perl--Test::Harness one
> that's now in emacs.  I believe the three symbols perl--Test,
> perl--Test2 and perl--Test::Harness can be replaced by the two simpler
> bits of compile.el.perl.fragment below.  compilation.txt fragment below
> too, to replace the two sections "* Perl Test module error messages" and
> "* Perl Test::Harness output".

[...]

> 2010-02-20  Kevin Ryde  <user42@zip.com.au>
>
> 	* compilation.txt (Perl Test module, Perl Test::Harness): Replace
> 	for new perl--Test and perl--Test-failed symbols.
>
>     (perl--Test
>      ;; Test.pm ok() message when comparing got/want values (printed in
>      ;; its _complain()),
>      ;;
>      ;;     # Test 2 got: "xx" (t-compilation-perl-2.t at line 10)
>      ;;
>      ;; And under Test::Harness can be preceded by progress stuff so
>      ;; allow match anywhere in the line.

[...]

> Yes.  It should be matched.  My latest and greatest seems to do so
> ( http://user42.tuxfamily.org/compilation-perl/index.html ).  I'll try
> to double check what I posted.
>
> Incidentally, the "cucumber" pattern of the emacs24 seems to match the
> perl test intro
>
> # Current time local: Wed Aug 15 12:04:58 2012
>
> I wondered if the cucumber "#" bit might be tightened up.  Maybe its "#"
> is never at the start of a line, or something like that.

It's been three years again, so it's time to revisit this bug report.
:-)

If this is still an issue, can you provide a patch for this instead of
code fragments?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2016-02-28  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20  0:15 bug#5607: 23.1; compile error regexps for perl test scripts, mark 2 Kevin Ryde
2012-12-02  6:11 ` Chong Yidong
2012-12-06 22:34   ` Kevin Ryde
2016-02-28  6:10 ` Lars Ingebrigtsen [this message]
2019-06-27 17:24   ` Lars Ingebrigtsen

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=87k2lptlfk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=5607@debbugs.gnu.org \
    --cc=user42@zip.com.au \
    /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).