From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Tue May  5 22:58:00 EDT 2020
Received: from abbatoir.fios-router.home (pool-162-83-132-245.nycmny.fios.verizon.net [162.83.132.245])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 370e4e27 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Tue, 5 May 2020 19:57:52 -0700 (PDT)
Message-ID: <722710B09E042E2040D082AE6A7C9216@eigenstate.org>
To: kvik@a-b.xyz, 9front@9front.org
Subject: Re: [9front] [PATCH] aux/getflags improvements
Date: Tue, 5 May 2020 19:57:51 -0700
From: ori@eigenstate.org
In-Reply-To: <B6A1FD8C36D20B71A9F9AA88958959FF@a-b.xyz>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: compliant singleton-aware SSL event storage hardware 

> This makes flagfmt= parser more admitting and convenient to
> use.
> 
> Any number of commas and newlines as well as any whitespace
> is eaten as a specifier separator.  This makes it so that
> a possibly long flagfmt can be broken up, like this:
> 
> 	flagfmt='
> 		a:all, b, 9,
> 		f:files f1 f2'
> 
> Is this worth a mention in the manpage?

Yes.
 
> Does this look alright to commit?

You'll need a corresponding change in aux/usage.

I also mildly prefer making '\n' equivalent to ' ' rather
than ',', but I'm not going to bikeshed that.