Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap check for new mail in the background
Date: Tue, 13 Dec 2005 17:24:36 +0100	[thread overview]
Message-ID: <iluvextj77f.fsf@latte.josefsson.org> (raw)
In-Reply-To: <83acf5f3c0.fsf@ntnu.no> (Lars Tobias =?iso-8859-1?Q?B=F8rsti?= =?iso-8859-1?Q?ng's?= message of "Tue, 13 Dec 2005 16:01:51 +0100")

Lars Tobias Børsting <lars.tobias.borsting@ntnu.no> writes:

>> It should not print the "Updating info" messages -- that will be much
>> slower than regular new mail checking.  It should only say "Quickly
>> checking mailbox foo", for each nnimap mailbox.
>
> It isn't saying "Quickly checking mailbox foo", it says "nnimap:
> Checking mailboxes...". It is also approximatelyten thousand times
> faster than before, so thanks a lot! :-)

This might depend on your gnus-verbose setting.

>> However, recently (perhaps last month) I have noticed that Gnus CVS
>> say "Updating info" for me too.  Not always, but sometimes.  So I
>> think we have another bug.
>
> So, it doesn't say "Updating info" anymore after I changed to
> "nnimap:foo".

I haven't seen it either for a while now.  I saw other problems as
well, and when I removed my entire Agent cache, they went away.

>>> Is it possible to do new mail checking in a separate thread that runs
>>> in the background, so that it doesn't lock up the interface? If not,
>>> is it hard to implement such a feature?
>>
>> It should be possible.  Implement something run with the idle timer
>> and iterate over all groups.  The problem is in informing Gnus about
>> the update -- there is no clean API to do that.  It could be added,
>> but I don't know how.
>
> Would it be possible to do what gnus-group-get-new-news-this-group does
> when updating each modified group?

(setq imap-log t) and look in the *imap-log* buffer, if you think of
the IMAP protocol exchange.

Otherwise, I recommend 'make tags' in .../gnus/lisp/ and then use of
edebug stepping.  (setq nnimap-debug t) and looking in the
*nnimap-debug* might be simpler, though.



  reply	other threads:[~2005-12-13 16:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09  3:20 Lars Tobias Børsting
2005-12-10 11:39 ` Simon Josefsson
2005-12-11  6:22   ` D. Michael McFarland
2005-12-12 15:52     ` Simon Josefsson
2005-12-13 14:45       ` Lars Tobias Børsting
2005-12-14  3:05         ` D. Michael McFarland
2005-12-14 14:14           ` Simon Josefsson
     [not found]             ` <ilufyovhil3.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2005-12-14 20:43               ` Jochen Küpper
2005-12-15 10:49                 ` Simon Josefsson
2005-12-13 15:01   ` Lars Tobias Børsting
2005-12-13 16:24     ` Simon Josefsson [this message]
2005-12-14 10:31       ` Lars Tobias Børsting
2005-12-14 14:12         ` Simon Josefsson

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=iluvextj77f.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).