From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 5D30D1F8C2;
	Mon,  8 Feb 2021 21:28:26 +0000 (UTC)
Date: Mon, 8 Feb 2021 20:28:26 -0100
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: TAP output for user-facing tools?
Message-ID: <20210208212826.GA20168@dcvr>
References: <20200622175128.GA6811@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200622175128.GA6811@dcvr>
List-Id: <meta.public-inbox.org>

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/