Re: [PATCH 0/9] argument parsing fixes and improvements

Subject: Re: [PATCH 0/9] argument parsing fixes and improvements

Date: Mon, 25 Sep 2017 17:57:38 -0300

To: Daniel Kahn Gillmor, Jani Nikula

Cc: Notmuch Mail

From: David Bremner

Daniel Kahn Gillmor <> 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 ;).


notmuch mailing list