From: Andrei POPESCU <andreimpopescu@gmail.com>
To: Austin Clements <amdragon@MIT.EDU>
Cc: notmuch@notmuchmail.org
Subject: Re: [RFC] http://notmuchmail.org/searching/ [was: Re: Improving notmuch query documentation]
Date: Sat, 17 Mar 2012 16:40:08 +0200 [thread overview]
Message-ID: <20120317144008.GB4510@sid.nuvreauspam> (raw)
In-Reply-To: <20120317002017.GG2670@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
On Vi, 16 mar 12, 20:20:17, Austin Clements wrote:
>
> It is, quite literally, the manpage. notmuch execs man when you run
> notmuch help.
Aha.
> 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.
Of course, I understand.
> > 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.
'git help' and 'man git' are quite different on my system, but I get the
point.
> > 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.
I still have a question: where does the first part of
'notmuch help search-terms' come from? I can't find the corresponding
section in the manpage? How about expanding that part just a bit and not
show the text that comes from the manpage?
Kind regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-03-17 14:40 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 [this message]
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=20120317144008.GB4510@sid.nuvreauspam \
--to=andreimpopescu@gmail.com \
--cc=amdragon@MIT.EDU \
--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).