From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@tethera.net>
Received: from localhost (localhost [127.0.0.1])
 by arlo.cworth.org (Postfix) with ESMTP id 006C46DE00DF
 for <notmuch@notmuchmail.org>; Mon, 25 Sep 2017 13:57:44 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011,
 SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled
Received: from arlo.cworth.org ([127.0.0.1])
 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id UMNebVbYSKhx for <notmuch@notmuchmail.org>;
 Mon, 25 Sep 2017 13:57:43 -0700 (PDT)
Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])
 by arlo.cworth.org (Postfix) with ESMTPS id 5559F6DE00C5
 for <notmuch@notmuchmail.org>; Mon, 25 Sep 2017 13:57:43 -0700 (PDT)
Received: from remotemail by fethera.tethera.net with local (Exim 4.89)
 (envelope-from <david@tethera.net>)
 id 1dwaO0-0001Yu-Jv; Mon, 25 Sep 2017 16:53:52 -0400
Received: (nullmailer pid 3999 invoked by uid 1000);
 Mon, 25 Sep 2017 20:57:38 -0000
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Jani Nikula <jani@nikula.org>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 0/9] argument parsing fixes and improvements
In-Reply-To: <8760c7x779.fsf@fifthhorseman.net>
References: <cover.1505853159.git.jani@nikula.org>
 <87mv5qxt3d.fsf@fifthhorseman.net>
 <CAB+hUn8+=jydtuSsscrZ6+8L-dshqeCZAJkzprYPJQ7fPqGg5A@mail.gmail.com>
 <87o9q5wlnj.fsf@fifthhorseman.net> <87k20st1yl.fsf@nikula.org>
 <87bmlz57wq.fsf@tethera.net> <8760c7x779.fsf@fifthhorseman.net>
Date: Mon, 25 Sep 2017 17:57:38 -0300
Message-ID: <8760c65we5.fsf@tethera.net>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Use and development of the notmuch mail system."
 <notmuch.notmuchmail.org>
List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 20:57:44 -0000

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> On Mon 2017-09-25 08:34:13 -0300, David Bremner wrote:
>> I think there is two different discussions one could be having here; one
>> about the UI, the other about the implimentation.
>>
>> From the UI point of view,
>
> Are you using the term "UI" to mean "API" here?  i tend to think of "UI"
> as the CLI interface, which i think still has open questions (see below).
>

when I say UI I mean CLI here.

> So from an implementation point of view, it's definitely cleaner/simpler
> to have an internally "explicitly unset" state for the CLI flags.

I'm trying to separate-out/defer impliementation questions here, at
least until I'm clear on the UI.

> From a CLI UI perspective: do we want to be able to send --foo=default
> for a boolean explicitly?

I have the feeling that maybe Jani does, but I'm not sure (as sometimes
happens) why my way of thinking about it isn't the only obvious way ;).

d