unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: David Bremner <david@tethera.net>, Jani Nikula <jani@nikula.org>,
	notmuch@notmuchmail.org
Subject: [Patch v2 1/4] doc: add material on stemming and wildcards
Date: Mon, 23 Feb 2015 21:05:34 +0100	[thread overview]
Message-ID: <1424721937-5797-2-git-send-email-david@tethera.net> (raw)
In-Reply-To: <1424721937-5797-1-git-send-email-david@tethera.net>

This is lightly massaged from the searching page on the wiki.
---
 doc/man7/notmuch-search-terms.rst | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/doc/man7/notmuch-search-terms.rst b/doc/man7/notmuch-search-terms.rst
index 54138d2..7fb4a27 100644
--- a/doc/man7/notmuch-search-terms.rst
+++ b/doc/man7/notmuch-search-terms.rst
@@ -135,6 +135,33 @@ operators, but will have to be protected from interpretation by the
 shell, (such as by putting quotation marks around any parenthesized
 expression).
 
+Stemming
+--------
+
+**Stemming** in notmuch means that these searches
+
+::
+
+        notmuch search detailed
+        notmuch search details
+        notmuch search detail
+
+will all return identical results, because Xapian first "reduces" the
+term to the common stem (here 'detail') and then performs the search.
+
+There are two ways to turn this off: a search for a capitalized word
+will be performed unstemmed, so that one can search for "John" and not
+get results for "Johnson"; phrase searches are also unstemmed (see
+below for details).  Stemming is currently only supported for
+English. Searches for words in other languages will be performed unstemmed.
+
+Wildcards
+---------
+
+It is possible to use a trailing '\*' as a wildcard. A search for
+'wildc\*' will match 'wildcard', 'wildcat', etc.
+
+
 Boolean and Probabilistic Prefixes
 ----------------------------------
 
-- 
2.1.4

  reply	other threads:[~2015-02-23 20:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18  9:33 [PATCH] doc: add details about Xapian search syntax David Bremner
2015-01-18 10:29 ` Jani Nikula
2015-01-18 12:59   ` [PATCH 1/3] " David Bremner
2015-01-18 12:59     ` [PATCH 2/3] doc: add material on stemming and wildcards David Bremner
2015-02-23 18:18       ` Jani Nikula
2015-01-18 12:59     ` [PATCH 3/3] doc: add more information on operators David Bremner
2015-02-23 18:23       ` Jani Nikula
2015-01-25 17:58     ` [PATCH 1/3] doc: add details about Xapian search syntax David Bremner
2015-02-23 20:05       ` David Bremner
2015-02-23 20:05         ` David Bremner [this message]
2015-02-23 20:05         ` [Patch v2 2/4] doc: add more information on operators David Bremner
2015-02-23 20:13           ` W. Trevor King
2015-02-23 20:05         ` [Patch v2 3/4] doc: typo fix for prefix discussion David Bremner
2015-02-23 20:05         ` [Patch v2 4/4] doc: update list of prefixes David Bremner
2015-02-24  7:32         ` 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=1424721937-5797-2-git-send-email-david@tethera.net \
    --to=david@tethera.net \
    --cc=jani@nikula.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).