unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Carl Worth <cworth@cworth.org>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] notmuch(1): clarify documentation about --option/value separators
Date: Fri, 08 May 2020 12:06:20 -0400	[thread overview]
Message-ID: <87v9l6mmwz.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87r1vv1fh1.fsf@wondoo.home.cworth.org>


[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]

On Thu 2020-05-07 16:40:26 -0700, Carl Worth wrote:
> On Thu, May 07 2020, Daniel Kahn Gillmor wrote:
>> +separator. Except for boolean options (wihch would be ambiguous), a
>
> Misspelling of "which". And while I'm here, strictly speaking Boolean is
> generally capitalized in English, (being one of those adjectives that is
> derived from a proper noun).
>
> Otherwise, this looks like a good improvement to me. Thanks!

Thanks for catching the "which" misspelling, which should obviously be
fixed if/when the patch is applied.  notmuch-search-terms(7) contains
both capitalized and non-capitalized spellings of "boolean".  I welcome
capitalization cleanup for this over the whole codebase, and hope that a
decision about this particular nit-pick isn't cause for delay of an
otherwise uncontroversial improvement.

      --dkg

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2020-05-08 16:10 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
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 [this message]
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=87v9l6mmwz.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=cworth@cworth.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).