notmuch(1): clarify documentation about --option/value separators

id:CA+Tk8fzRiqxWpd=r8=DRvEewNZXUZgD7MKyRLB1A=R-LxxGEZw@mail.gmail.com
started a thread of discussion that showed that the cli's current
idiosyncrasies around dealing with boolean options were not
understandable.

This attempts to improve the documentation at least (actual changes to
the API might be better, but have not reached consensus).

Note that no one in the discussion thread identified any other
(non-boolean) command-line options that cannot use space as a
separator.  If such an option is identified (or introduced in the
future), it should be added explicitly to this part of the manual.

Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
This commit is contained in:
Daniel Kahn Gillmor 2020-05-07 15:26:45 -04:00 committed by David Bremner
parent 45cfeb2e55
commit 02a2bf1b25

View file

@ -128,9 +128,9 @@ OPTION SYNTAX
------------- -------------
All options accepting an argument can be used with '=' or ':' as a All options accepting an argument can be used with '=' or ':' as a
separator. For the cases where it's not ambiguous (in particular separator. Except for boolean options (which would be ambiguous), a
excluding boolean options), a space can also be used. The following space can also be used as a separator. The following are all
are all equivalent: equivalent:
:: ::