From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED,
	RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from out1.migadu.com (out1.migadu.com [91.121.223.63])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 49FFD1F934
	for <meta@public-inbox.org>; Wed, 23 Dec 2020 15:49:08 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1;
	t=1608738546;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=BNy/Xbx4dBN1IUmSlxxP+Z2lUKjQ6f72aVwdiZ4zz88=;
	b=Mt94KNclLEfNNR3+ICG25LZ45Uhw5OZFX9gYfFnmAvAqog2AIPPbElvdJaYECO1Q00swVy
	KcidpUqdPnOJtLHBKBA+Jb9jsB19ntgkKhUFMzSJ7psPZyWez/gOeLDmbJ1ESVnsn1l1fg
	yRt25CTWF7ui77Hl6QdwERginlyAij9VieEnlWBkxFxksk9jNc11O19AQhmywY7MjCuMba
	Ny9IxYevoLKMyq/UDZcQxg6q/harFGL+Wf81i9L8KxedaLGw7GZFKSEWP4f4BMlZqFigQj
	TH1jQgqd2/76Z9Z8SZgkuoc3qdZjHHn6p1mRBvOqkLMYeDW7xp4ktva5LWJCVw==
From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: more considerations in UI/UX...
In-Reply-To: <20201223094744.GA30957@dcvr>
References: <20201215120544.GA8927@dcvr> <87ft3xgjse.fsf@kyleam.com>
 <20201223094744.GA30957@dcvr>
Message-ID: <874kkch6a7.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: kyle@kyleam.com
Date: Wed, 23 Dec 2020 15:49:06 GMT
List-Id: <meta.public-inbox.org>

Eric Wong writes:

> Yes, leaving JSON out of "lei q(uery)" output was an oversight,
> and probably "show", too...  I'm also wondering if there'll need
> to be multiple flavors of JSON output for compatibility with
> existing tools: "nm-json", "foo-json", "bar-json", etc..

Ah, sorry, I should have been clearer here.  Perhaps others would have a
use for tool-specific JSON, but it's really just having some sort of
structured output that I'm interested in.  With the notmuch output, I
was trying to give a sense of what it looked like in notmuch's case.
Whatever JSON output fits and makes sense for public-inbox, I can gladly
work with :)