Re: Inconsistencies in handling command flags: `--flag=value` different than `--flag value`

Subject:Re: Inconsistencies in handling command flags: `--flag=value` different than `--flag value`

Date:Wed, 29 Apr 2020 12:39:11 -0300

To:Daniel Kahn Gillmor ,Jani Nikula

Cc:notmuch@notmuchmail.org

From:David Bremner


Tomi Ollila <tomi.ollila@iki.fi> writes:

> On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
>
>>
>> One final way we could normalize everything and make it less
>> idiosyncratic, with shorter, simpler man pages: deprecate and then drop
>> the --booloption/--no-booloption mechanisms, requiring --booloption=true
>> or --booloption=false instead.  Once they're dropped, allow whitespace
>> between "--booloption true" and "--booloption false" just like every
>> other type of option.
>
> I must say, being it perhaps slightly inconvenient to the user, that
> this is IMO the best option, and just allowing 'true' and 'false'
> (case-sensitively). Least chance to work how used did not expected...
>

I guess I'm a bit leery of removing UI features that presumably at least
some people rely on. It's pretty upsetting to have sofware break one's
muscle memory.

d
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Thread: