Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: IMAP + Agent
Date: Wed, 24 Aug 2011 15:45:48 +0100	[thread overview]
Message-ID: <87ty96dg0z.fsf@ucl.ac.uk> (raw)
In-Reply-To: <73y5yjnijn.fsf@news.eternal-september.org> (Richard Riley's message of "Wed, 24 Aug 2011 13:41:16 +0200")

Richard Riley <rileyrg@googlemail.com> writes:

> Steinar Bang <sb@dod.no> writes:
>
>>>>>>> Frank Schmitt <ich@frank-schmitt.net>:
>>
>>> Steinar Bang <sb@dod.no> writes:
>>
>>>> The old nnimap and the agent used to work, more or less.  I even had
>>>> cache-when-read working.
>>
>>> No way. In the days when I was more active in #gnus and the Gnus
>>> Newsgroup, 50% of all IMAP related problems could be solved by
>>> disabling the Agent.
>>
>> "used to work for me", I meant to write.
>>
>> I can't speak for others.
>
> Well, my OP had the result I intended. Its quite clear it doesnt work
> for anyone after all ;) I was wondering if it was "just me"...

Well, IMAP + Gnus agents work for me, with the following caveats:

1. I only have one account per imap server and

2. when I want to update the agent (J s), I quit gnus, restart it and
   then download.

The second point is critical, in my experience.  If I have done anything
with gnus (reading, expiring, whatever), then the agent gets confused.
I cannot reproduce the problems at will but ever since I started doing
the download *only* immediately after starting gnus, everything has
worked fine.  

I make use of the agent for offline work twice daily for my long train
commutes.  Couldn't function anywhere near as well without it.  I used
to use offlineimap but moved to gnus completely when it improved so
dramatically last year and because it looked like offlineimap was being
orphaned...

HTH,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.18



  reply	other threads:[~2011-08-24 14:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  0:48 Richard Riley
2011-08-24  1:08 ` John Wiegley
2011-08-24  1:50   ` Richard Riley
2011-08-24  8:20     ` Steinar Bang
2011-08-24  9:15       ` Frank Schmitt
2011-08-24 10:01         ` Tassilo Horn
2011-08-24 15:32           ` Steinar Bang
2011-08-24 16:29             ` Tassilo Horn
2011-08-24 11:00         ` Steinar Bang
2011-08-24 11:41           ` Richard Riley
2011-08-24 14:45             ` Eric S Fraga [this message]
2011-08-24 15:19               ` Richard Riley
2011-08-24 15:22                 ` Eric S Fraga
2011-08-24 15:36               ` Steinar Bang
2011-08-24 22:10                 ` Eric S Fraga
2011-09-27 21:36         ` Ted Zlatanov
2011-09-28  7:04           ` Reiner Steib
2011-09-29  0:26             ` Ted Zlatanov
2011-10-06 21:28           ` Lars Magne Ingebrigtsen
     [not found]   ` <87d3fjijlw.fsf@noorul.collab.net>
2011-09-05 18:12     ` John Wiegley
2011-08-24  3:05 ` Vijay Lakshminarayanan
2011-08-24  6:01   ` Richard Riley
2011-08-24 15:12     ` Vijay Lakshminarayanan

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=87ty96dg0z.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).