From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: info-gnus-english@gnu.org
Subject: Re: [RFC] Gnus generalized search, part II
Date: Fri, 28 Apr 2017 09:18:50 +0100 [thread overview]
Message-ID: <87zif16j2t.fsf@delle7240> (raw)
In-Reply-To: <cb06d28e83ab4a6cab1b3cd02fc7e554@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Andrew Cohen's message of "Fri, 28 Apr 2017 01:18:53 +0000")
[-- Attachment #1.1: Type: text/plain, Size: 922 bytes --]
On Friday, 28 Apr 2017 at 01:18, Andrew Cohen wrote:
> 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.
I don't have any local index (as far as I know). I simply enable the
agent to ensure I can read my emails off-line (I spend 2-3 hours a day
off-line while commuting).
> It would be helpful if you could checkout feature/gnus-select and see
> what happens :)
Is this from the emacs repository or is there a separate gnus one? In
either case, where is it located please?
Thanks,
eric
--
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
prev parent reply other threads:[~2017-04-28 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zif930mt.fsf@ericabrahamsen.net>
[not found] ` <m3lgqsz0am.fsf@stories>
[not found] ` <87shkx5z17.fsf@ericabrahamsen.net>
[not found] ` <874lxbhjam.fsf@hanan>
[not found] ` <7e7ccca805864b5398551cc74123df11@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-27 14:30 ` Eric S Fraga
[not found] ` <cb06d28e83ab4a6cab1b3cd02fc7e554@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-28 8:18 ` Eric S Fraga [this message]
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=87zif16j2t.fsf@delle7240 \
--to=e.fraga@ucl.ac.uk \
--cc=info-gnus-english@gnu.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).