From: Julien Cubizolles <j.cubizolles@free.fr>
To: ding@gnus.org
Subject: Re: Agent in batch mode for imap
Date: Wed, 16 Jan 2013 14:42:33 +0100 [thread overview]
Message-ID: <87ehhl2qie.fsf@free.fr> (raw)
In-Reply-To: <871udmdkla.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> I guess the agent confuses itself when it splits a message to the
>> same group it splitted it from and counts it twice. Looks like a
>> bug ?
>
> Whether it's a bug or not, it is rather inefficient as you will be
> processing any such messages over and over again! Seems cleaner to
> split to elsewhere regardless.
You're right, but I've been using this inefficient process for a while
now and only recently switched to running unplugged so It took me a
while to notice this behaviour.
prev parent reply other threads:[~2013-01-16 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87623dfh85.fsf@free.fr>
[not found] ` <87r4m1j9ii.fsf@free.fr>
[not found] ` <877gnshm9e.fsf@gmail.com>
[not found] ` <877gng5bry.fsf@free.fr>
2013-01-14 22:08 ` Eric S Fraga
2013-01-15 22:04 ` Julien Cubizolles
2013-01-16 0:42 ` Eric S Fraga
2013-01-16 13:42 ` Julien Cubizolles [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=87ehhl2qie.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).