unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>, notmuch@notmuchmail.org
Subject: Re: correct way to search for only PDF attachments
Date: Tue, 29 Sep 2015 10:48:24 -0300	[thread overview]
Message-ID: <87bncljpzr.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <20150929115600.GR15858@chitra.no-ip.org>

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> On Tue, Sep 29, 2015 at 08:00:18AM -0300, David Bremner wrote:
>>
>> Of course it is getting pretty big, I don't know what to do about
>> that.
>
> How about an overview in notmuch-search-terms with more detailed docs in
> an info page?  coreutils does this.  I don't think this will add any new
> build dependencies either, as sphinx supports info pages.  I see
> texinfo_documents is already defined in doc/conf.py.  Maybe that is an
> option?
>

I'm not really in favour of requiring anyone who is not already using
emacs to use info.  Of course we could provide the same long form docs
in other formats (most likely html).  I don't know if splitting into
shorter man pages plus a longer manual would really help, but it's
likely we could take better advantage of sphinx. I know that Patrick
Totzke started a rework of the docs

       https://github.com/pazz/notmuch/tree/docs

I don't think that's really in a state to contemplate merging (for one
thing it hasn't kept up with doc changes in master); but maybe somebody
wants to pick up where Patrick left off.

d

  reply	other threads:[~2015-09-29 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  0:55 correct way to search for only PDF attachments Xu Wang
2015-09-29  2:00 ` Carl Worth
2015-09-29  4:51   ` Xu Wang
2015-09-29  7:15   ` Suvayu Ali
2015-09-29 11:00   ` David Bremner
2015-09-29 11:56     ` Suvayu Ali
2015-09-29 13:48       ` David Bremner [this message]
2015-09-30 15:16         ` Xu Wang

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=87bncljpzr.fsf@tesseract.cs.unb.ca \
    --to=david@tethera.net \
    --cc=fatkasuvayu+linux@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).