From: Peter Wang <novalazy@gmail.com>
To: notmuch@notmuchmail.org
Subject: [PATCH] doc: fix references to search.exclude_tags
Date: Sun, 27 Jan 2019 17:54:59 +1100 [thread overview]
Message-ID: <20190127065459.4953-1-novalazy@gmail.com> (raw)
The documentation incorrectly referred to a configuration item
"search.tag_exclude" in some places, instead of "search.exclude_tags".
---
doc/man1/notmuch-address.rst | 2 +-
doc/man1/notmuch-count.rst | 2 +-
doc/man1/notmuch-search.rst | 2 +-
doc/man1/notmuch-show.rst | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/man1/notmuch-address.rst b/doc/man1/notmuch-address.rst
index 12d86e89..2a7df6f0 100644
--- a/doc/man1/notmuch-address.rst
+++ b/doc/man1/notmuch-address.rst
@@ -92,7 +92,7 @@ Supported options for **address** include
``--exclude=(true|false)``
A message is called "excluded" if it matches at least one tag in
- search.tag\_exclude that does not appear explicitly in the search
+ search.exclude\_tags that does not appear explicitly in the search
terms. This option specifies whether to omit excluded messages in
the search process.
diff --git a/doc/man1/notmuch-count.rst b/doc/man1/notmuch-count.rst
index 9ca20dab..0eac5dbe 100644
--- a/doc/man1/notmuch-count.rst
+++ b/doc/man1/notmuch-count.rst
@@ -36,7 +36,7 @@ Supported options for **count** include
same message-id).
``--exclude=(true|false)``
- Specify whether to omit messages matching search.tag\_exclude from
+ Specify whether to omit messages matching search.exclude\_tags from
the count (the default) or not.
``--batch``
diff --git a/doc/man1/notmuch-search.rst b/doc/man1/notmuch-search.rst
index 654c5f2c..ed9ff4e5 100644
--- a/doc/man1/notmuch-search.rst
+++ b/doc/man1/notmuch-search.rst
@@ -100,7 +100,7 @@ Supported options for **search** include
``--exclude=(true|false|all|flag)``
A message is called "excluded" if it matches at least one tag in
- search.tag\_exclude that does not appear explicitly in the search
+ search.exclude\_tags that does not appear explicitly in the search
terms. This option specifies whether to omit excluded messages in
the search process.
diff --git a/doc/man1/notmuch-show.rst b/doc/man1/notmuch-show.rst
index a2708a04..becd3e79 100644
--- a/doc/man1/notmuch-show.rst
+++ b/doc/man1/notmuch-show.rst
@@ -161,7 +161,7 @@ Supported options for **show** include
Default: ``auto``
``--exclude=(true|false)``
- Specify whether to omit threads only matching search.tag\_exclude
+ Specify whether to omit threads only matching search.exclude\_tags
from the search results (the default) or not. In either case the
excluded message will be marked with the exclude flag (except when
output=mbox when there is nowhere to put the flag).
--
2.20.1
next reply other threads:[~2019-01-27 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 6:54 Peter Wang [this message]
2019-01-27 12:23 ` [PATCH] doc: fix references to search.exclude_tags David Bremner
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=20190127065459.4953-1-novalazy@gmail.com \
--to=novalazy@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).