Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: any partial or rudamentary documentation of new nnselect work somewhere?
Date: Sat, 06 May 2017 18:39:53 -0400	[thread overview]
Message-ID: <86r301wqx2.fsf@local.lan> (raw)

I'd like to get my hands on some bit of docu for the new nnselect work
that is being done... I realize it is not done and won't be for some
time.

But I need a start of some kind.  Such things as the search syntax
and something explaining the basics of how the search terms need to
work with many backends.  That is, some big picture explanations and
possibly as many actual examples as anyone has time to write.

Something as rough as some of the experts working on nnselect might
save there test command lines off to a file ... even with no
explanatory remarks and make that available somewhere.

I've followed the discussion to the best of my ability... but mostly
its over my head.

I would still like to do some testing and I suspect the work needs to
have a few non-expert testers at some point to make sure the new work
is usable to some of us dim wits too.




             reply	other threads:[~2017-05-06 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 22:39 Harry Putnam [this message]
2017-05-07  0:10 ` Andrew Cohen
2017-05-10 20:49   ` Harry Putnam
2017-05-11  0:01     ` Andrew Cohen
2017-05-11 13:07       ` Harry Putnam
2017-05-12  1:18         ` Eric Abrahamsen
2017-05-13 13:44           ` Harry Putnam
2017-05-14  2:48             ` Eric Abrahamsen
2017-05-14 13:21               ` Harry Putnam
2017-05-14 13:24               ` Harry Putnam
2017-05-15  3:30                 ` Eric Abrahamsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86r301wqx2.fsf@local.lan \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).