user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: TAP output for user-facing tools?
Date: Mon, 22 Jun 2020 17:51:28 +0000	[thread overview]
Message-ID: <20200622175128.GA6811@dcvr> (raw)

Hey all, so I've been wondering about how to express
debug/tracing output to user-facing command-line tools.

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*

TAP = Test Anything Protocol:

             reply	other threads:[~2020-06-22 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 17:51 Eric Wong [this message]
2021-02-08 21:28 ` Eric Wong

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200622175128.GA6811@dcvr \ \ \
    --subject='Re: TAP output for user-facing tools?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).