From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: Inconsistencies in handling command flags: `--flag=value` different than `--flag value`
Date: Wed, 29 Apr 2020 12:39:11 -0300 [thread overview]
Message-ID: <87pnbql2sg.fsf@tethera.net> (raw)
In-Reply-To: <m28sie1ikw.fsf@guru.guru-group.fi>
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
next prev parent reply other threads:[~2020-04-29 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 12:53 Inconsistencies in handling command flags: `--flag=value` different than `--flag value` Ciprian Dorin Craciun
2020-04-27 17:53 ` David Bremner
2020-04-27 18:02 ` Daniel Kahn Gillmor
2020-04-27 18:20 ` Tomi Ollila
2020-04-27 19:21 ` Ciprian Dorin Craciun
2020-04-29 2:16 ` Daniel Kahn Gillmor
2020-04-29 14:18 ` Tomi Ollila
2020-04-29 15:39 ` David Bremner [this message]
2020-04-29 15:45 ` Jameson Graef Rollins
2020-04-29 16:28 ` David Bremner
2020-05-05 18:28 ` Carl Worth
2020-05-07 19:26 ` [PATCH] notmuch(1): clarify documentation about --option/value separators Daniel Kahn Gillmor
2020-05-07 23:40 ` Carl Worth
2020-05-08 12:01 ` David Bremner
2020-05-08 16:06 ` Daniel Kahn Gillmor
2020-04-29 15:59 ` Inconsistencies in handling command flags: `--flag=value` different than `--flag value` Ciprian Dorin Craciun
2020-04-29 16:07 ` Jameson Graef Rollins
2020-04-29 15:33 ` Jameson Graef Rollins
2020-04-30 16:59 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnbql2sg.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).