user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
* TAP output for user-facing tools?
@ 2020-06-22 17:51 Eric Wong
  2021-02-08 21:28 ` Eric Wong
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Wong @ 2020-06-22 17:51 UTC (permalink / raw)
  To: meta

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: https://testanything.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: TAP output for user-facing tools?
  2020-06-22 17:51 TAP output for user-facing tools? Eric Wong
@ 2021-02-08 21:28 ` Eric Wong
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2021-02-08 21:28 UTC (permalink / raw)
  To: meta

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-02-08 21:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-22 17:51 TAP output for user-facing tools? Eric Wong
2021-02-08 21:28 ` Eric Wong

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
		meta@public-inbox.org
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git