Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@bu.edu>
To: ding@gnus.org
Subject: Re: [RFC] Gnus generalized search, part II
Date: Fri, 28 Apr 2017 09:18:53 +0800	[thread overview]
Message-ID: <87mvb1z5vm.fsf@hanan> (raw)
In-Reply-To: <87k2653oum.fsf@delle7240>

>>>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

    Eric> On Wednesday, 26 Apr 2017 at 15:51, Eric Abrahamsen wrote:
    >> Andrew Cohen <cohen@bu.edu> writes:

    Eric> [...]

    >>> (Who is beginning to think that you and I are the only two who
    >>> will ever use this new stuff).
    >> 
    >> I was starting to think the same thing! Glad to see others
    >> chiming in.

    Eric> I know that I would likely use this and would definitely do so
    Eric> if the generalised search interface included off-line use with
    Eric> the agent...  not sure if that is planned or even possible but
    Eric> thought I would mention it!


It should work, but its totally untested (I don't use the agent). The
nnselect backend (which is independent of searching) should act like any
backend and use the agent as appropriate (although since it hasn't been
tested it is probably buggy). The searching part should behave as (the
other) Eric indicated: searches in local indices should work fine, and
searches that require a network connection should signal an error.


It would be helpful if you could checkout feature/gnus-select and see
what happens :)

Best,
Andy




  parent reply	other threads:[~2017-04-28  1:18 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 21:35 Eric Abrahamsen
2017-04-22  0:16 ` Andrew Cohen
2017-04-22  7:50   ` Eli Zaretskii
2017-04-22  8:00     ` Andrew Cohen
2017-04-22 19:53 ` Lars Ingebrigtsen
2017-04-22 20:26   ` Eric Abrahamsen
2017-04-24 20:30   ` Eric Abrahamsen
2017-04-26  4:41     ` Andrew Cohen
2017-04-26  6:31       ` Adam Sjøgren
2017-04-26  7:39         ` Saša Janiška
2017-04-26 16:07           ` Eric Abrahamsen
2017-04-26  9:21       ` Joakim Jalap
2017-04-26 15:51       ` Eric Abrahamsen
     [not found]       ` <7e7ccca805864b5398551cc74123df11@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
     [not found]         ` <87k2653oum.fsf@delle7240>
2017-04-27 19:35           ` Eric Abrahamsen
2017-04-28  1:18           ` Andrew Cohen [this message]
     [not found]           ` <cb06d28e83ab4a6cab1b3cd02fc7e554@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
     [not found]             ` <87zif16j2t.fsf@delle7240>
2017-04-28  9:16               ` Andrew Cohen
2017-04-26  8:18     ` Andrew Cohen
2017-04-26 16:37       ` Eric Abrahamsen
2017-04-26 22:31         ` Eric Abrahamsen
2017-04-27  4:27           ` Andrew Cohen
2017-04-27 18:22             ` Eric Abrahamsen
2017-04-28  1:15               ` Andrew Cohen
2017-04-28 18:23                 ` Eric Abrahamsen
2017-04-28 20:52                   ` Eric Abrahamsen
2017-04-28 23:26                     ` Andrew Cohen
2017-04-29  3:57                       ` Eric Abrahamsen
2017-04-29  9:37                         ` Andrew Cohen
2017-04-30  5:13                           ` Eric Abrahamsen
2017-04-28 23:34                   ` Andrew Cohen
2017-04-29  4:16                     ` Eric Abrahamsen
2017-04-29 21:20                 ` Harry Putnam
2017-04-30  0:15                   ` Andrew Cohen
2017-04-26 17:50       ` Eric Abrahamsen
2017-04-26  8:22     ` Andrew Cohen
2017-04-23 13:48 ` Dan Christensen
2017-04-23 17:19   ` Eric Abrahamsen
2017-04-23 17:59     ` Dan Christensen
2017-04-23 23:22       ` Eric Abrahamsen
2017-04-24  1:37         ` Dan Christensen
2017-04-24 21:02           ` Eric Abrahamsen
2017-06-10  4:46     ` 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=87mvb1z5vm.fsf@hanan \
    --to=cohen@bu.edu \
    --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).