From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: TAP output for user-facing tools?
Date: Mon, 8 Feb 2021 20:28:26 -0100 [thread overview]
Message-ID: <20210208212826.GA20168@dcvr> (raw)
In-Reply-To: <20200622175128.GA6811@dcvr>
Eric Wong wrote:
> Hey all, so I've been wondering about how to express
> debug/tracing output to user-facing command-line tools.
So I've started using "#" for diagnostic/progress messages in
lei.
I may replace "I:" prefixed messages with them, at least in lei.
"W:" and "E:" will probably stay for warnings and errors,
respectively, but maybe "# W:" and "# E:" ?
> Our test suite already uses TAP. So does git.git, Perl itself
> and the majority of Perl projects I've encountered.
>
> But I haven't seen it used for user-facing CLI tools...
> It seems better than inventing random new formats *shrug*
Other messages ("ok", "not ok", 1..$TEST_NR) may make sense
for "lei import", but not "lei q".
> TAP = Test Anything Protocol: https://testanything.org/
prev parent reply other threads:[~2021-02-08 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 17:51 TAP output for user-facing tools? Eric Wong
2021-02-08 21:28 ` Eric Wong [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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210208212826.GA20168@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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.
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).