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

2020-05-05 Thread Carl Worth
On Wed, Apr 29 2020, Jameson Graef Rollins wrote: > I dare say there are few people that have muscle memory for the notmuch > command line (especially for notmuch show), and fewer that aren't > themselves developers... Here, the concern isn't just "muscle memory" (forcing users to learn how to

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

2020-04-30 Thread Daniel Kahn Gillmor
On Wed 2020-04-29 08:33:24 -0700, Jameson Graef Rollins wrote: > 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

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

2020-04-29 Thread David Bremner
Jameson Graef Rollins writes: > On Wed, Apr 29 2020, David Bremner wrote: >> 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. > > I dare say there are few people that have muscle

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

2020-04-29 Thread Jameson Graef Rollins
On Wed, Apr 29 2020, Ciprian Dorin Craciun wrote: > I think there are two complete different use-cases for the `notmuch` binary: > * a simple CLI to query the database, in which case the current flags seem OK; > * a "poor-mans" API to query the database, more bellow; > > (I know there already

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

2020-04-29 Thread Ciprian Dorin Craciun
On Wed, Apr 29, 2020 at 6:39 PM David Bremner wrote: > 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. I think there are two complete different use-cases for the `notmuch` binary:

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

2020-04-29 Thread Jameson Graef Rollins
On Wed, Apr 29 2020, David Bremner wrote: > 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. I dare say there are few people that have muscle memory for the notmuch command line

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

2020-04-29 Thread David Bremner
Tomi Ollila 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

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

2020-04-29 Thread Jameson Graef Rollins
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.

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

2020-04-29 Thread Tomi Ollila
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.

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

2020-04-28 Thread Daniel Kahn Gillmor
On Mon 2020-04-27 22:21:36 +0300, Ciprian Dorin Craciun wrote: > On Mon, Apr 27, 2020 at 9:21 PM Tomi Ollila wrote: >>> [dkg wrote:] >>> release, remove the suggestion to use a whitespace separator from the >>> documentation, and eventually phase it out entirely in some future >>> release. >> >>

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

2020-04-27 Thread Ciprian Dorin Craciun
On Mon, Apr 27, 2020 at 9:21 PM Tomi Ollila wrote: > > On Mon 2020-04-27 14:53:07 -0300, David Bremner wrote: > >> Quoting notmuch(1) > >> > >>OPTION SYNTAX > >>All options accepting an argument can be used with '=' > >>or ':' as a separator. For the cases where it's not

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

2020-04-27 Thread Tomi Ollila
On Mon, Apr 27 2020, Daniel Kahn Gillmor wrote: > On Mon 2020-04-27 14:53:07 -0300, David Bremner wrote: >> Quoting notmuch(1) >> >>OPTION SYNTAX >>All options accepting an argument can be used with '=' >>or ':' as a separator. For the cases where it's not ambiguous >>

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

2020-04-27 Thread Daniel Kahn Gillmor
On Mon 2020-04-27 14:53:07 -0300, David Bremner wrote: > Quoting notmuch(1) > >OPTION SYNTAX >All options accepting an argument can be used with '=' >or ':' as a separator. For the cases where it's not ambiguous >(in particular excluding boolean options), a space can

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

2020-04-27 Thread David Bremner
Ciprian Dorin Craciun writes: > [Again sorry for double reporting. BTW, where should I search for > previous bugs? I've currently tried the mailing list archive.] Another option is https://nmbug.notmuchmail.org/status This is just pointers into the mailing archive, but triaged. > >

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

2020-04-24 Thread Ciprian Dorin Craciun
[Again sorry for double reporting. BTW, where should I search for previous bugs? I've currently tried the mailing list archive.] Trying to play with `notmuch` from a wrapper, I've stumbled upon the following command line flags handling bug: notmuch show --format json --entire-thread true