unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Austin Clements <amdragon@MIT.EDU>
To: Andrei POPESCU <andreimpopescu@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [RFC] http://notmuchmail.org/searching/ [was: Re: Improving notmuch query documentation]
Date: Fri, 16 Mar 2012 20:20:17 -0400	[thread overview]
Message-ID: <20120317002017.GG2670@mit.edu> (raw)
In-Reply-To: <20120316222952.GA4510@sid.nuvreauspam>

Quoth Andrei POPESCU on Mar 17 at 12:29 am:
> On Jo, 15 mar 12, 22:11:24, Austin Clements wrote:
> > Quoth Andrei POPESCU on Mar 16 at  2:30 am:
> > > 
> > > $ 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 not quite sure what you mean.  That text is the man page.  Though
> > it sounds like a great idea to have a quick syntax reference at the
> > top of the manpage so it's the first thing people see when they run
> > 'notmuch help search-terms' (and they can still scroll down to get the
> > details if they want).
> 
> On Vi, 16 mar 12, 13:52:35, David Bremner wrote:
> > On Fri, 16 Mar 2012 02:30:53 +0200, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
> > 
> > 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.
> 
> What I mean is that 'notmuch help search-terms' is too verbose. IMHO 
> there should be very good reasons to have it longer than 20 lines or so. 
> Instead it's the entire section 'SEARCH SYNTAX' from the manpage.

It is, quite literally, the manpage.  notmuch execs man when you run
notmuch help.

This was an intentional change a few releases ago.  Previously, we did
have separate manpages and internal help documentation and it didn't
work very well since they were perpetually out of sync.  Hence the
general concern about documentation fragmentation.

> This opinion is based also on what I see around at other terminal 
> applications. The '--help' is seldom longer than a few lines and just 
> lists the available options and parameters (more like a refresher). The 
> manpage then explains them in more detail.

That's true of simple commands, but most commands with subcommands
follow a style like notmuch.  In fact, notmuch's approach was modeled
directly off of git, and most modern VCSs do similar things.

> As I see it, the manpage (specifically section 'SEARCH SYNTAX' needs to 
> be expanded somewhat and 'help search-terms' shortened (a lot).

What did you think of my suggestion that the first thing in man
search-terms be a short reference so that's what you see immediately
when you run notmuch help search-terms?  That seems to accomplish what
you want without fragmenting the documentation and seems like a good
way to write the documentation anyway.

  parent reply	other threads:[~2012-03-17  0:20 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 [this message]
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

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=20120317002017.GG2670@mit.edu \
    --to=amdragon@mit.edu \
    --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).