From: David Bremner <david@tethera.net>
To: Andrei POPESCU <andreimpopescu@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [RFC] http://notmuchmail.org/searching/ [was: Re: Improving notmuch query documentation]
Date: Fri, 16 Mar 2012 13:52:35 -0300 [thread overview]
Message-ID: <87r4wso5d8.fsf@convex-new.cs.unb.ca> (raw)
In-Reply-To: <20120316003053.GR2981@sid.nuvreauspam>
On Fri, 16 Mar 2012 02:30:53 +0200, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
>
> Regarding 'notmuch help search-terms':
>
> $ notmuch help search-terms | wc -l
> 88
>
> IMHO that text is better suited for a manpage, the help should be just a
> (very short) reference to refresh ones memory. What do you think?
>
I'm less worried about the length of the documentation than about
fragmentation. So I think if something is reference material, it should
go in the man pages, or at least ship with notmuch.
d
prev parent reply other threads:[~2012-03-16 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:06 Partial words on notmuch search? Andrei Popescu
2012-01-16 1:07 ` mailinglists
2012-01-16 20:21 ` Andrei Popescu
2012-01-16 22:26 ` David Bremner
2012-01-16 22:38 ` Andrei Popescu
2012-01-17 2:34 ` Austin Clements
2012-01-17 17:43 ` Jani Nikula
2012-01-17 19:47 ` Austin Clements
2012-01-17 22:14 ` Improving notmuch query documentation [was: Re: Partial words on notmuch search?] Andrei Popescu
2012-01-17 22:29 ` Austin Clements
2012-01-20 19:08 ` Mark Anderson
2012-03-15 21:15 ` Austin Clements
2012-03-15 9:39 ` [RFC] http://notmuchmail.org/searching/ [was: Re: Improving notmuch query documentation] Andrei POPESCU
2012-03-15 21:11 ` Austin Clements
2012-03-16 0:30 ` Andrei POPESCU
2012-03-16 2:11 ` Austin Clements
2012-03-16 22:29 ` Andrei POPESCU
2012-03-16 23:51 ` David Bremner
2012-03-17 0:20 ` Austin Clements
2012-03-17 14:40 ` Andrei POPESCU
2012-03-17 17:16 ` Austin Clements
2012-03-17 19:59 ` Andrei POPESCU
2012-03-16 16:52 ` David Bremner [this message]
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=87r4wso5d8.fsf@convex-new.cs.unb.ca \
--to=david@tethera.net \
--cc=andreimpopescu@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).