unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>,
	notmuch@notmuchmail.org
Subject: Re: Inconsistencies in handling command flags: `--flag=value` different than `--flag value`
Date: Mon, 27 Apr 2020 14:53:07 -0300	[thread overview]
Message-ID: <87imhk95oc.fsf@tethera.net> (raw)
In-Reply-To: <CA+Tk8fzRiqxWpd=r8=DRvEewNZXUZgD7MKyRLB1A=R-LxxGEZw@mail.gmail.com>

Ciprian Dorin Craciun <ciprian.craciun@gmail.com> 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.

>
> 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 --body false --
> 'ciprian@volution.ro'
> notmuch show --format json --entire-thread true --body=false --
> 'ciprian@volution.ro'

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 also be
       used.

So what you are seeing is a side effect of "--entire-thread true" not
being supported syntax.

You can see what's happening with

 NOTMUCH_DEBUG_QUERY=t notmuch show --format json --entire-thread true djkldsfjkl

the "true" is considered the first search term.

In your example you could just delete the "true" to switch on the
option.

  reply	other threads:[~2020-04-27 17:53 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 [this message]
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
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=87imhk95oc.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=ciprian.craciun@gmail.com \
    --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).