Gnus development mailing list
 help / color / mirror / Atom feed
From: Johan Parin <Johan.Parin@abc.se>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Mail Fetching (was: Re: IMAP Questions)
Date: 07 Jun 2000 20:35:13 +0200	[thread overview]
Message-ID: <m3og5dxrtq.fsf_-_@johanspc.abc.se> (raw)
In-Reply-To: Simon Josefsson's message of "07 Jun 2000 02:16:48 +0200"


Simon Josefsson writes:

  Simon> Johan Parin <Johan.Parin@abc.se> writes:
  >> >> (gnus-demon-add-handler 'gnus-demon-scan-mail 2 nil)
  Simon> ...
  >> You're right. Tried it at home, where I'm using pop, and it's the same 
  >> problem. I hope I'm not misunderstanding something - I mean
  >> gnus-demon-scan-mail _is_ supposed to fetch new mail, right?

  Simon> Perhaps `gnus-demon-scan-news' is what you want?  By the look
  Simon> of the code, `g-d-s-mail' only scan (ie perform splitting),
  Simon> and `g-d-s-news' does the same but also update the group
  Simon> buffer.

g-d-s-news does the job alright but it's not what I want - I just want 
to fetch new mail, not news. I don't understand what it means to only
perform splitting - what mail is split if no new mail is fetched?

  >> Anyway, I did some more debugging and what happens is that when
  >> nnmail-get-new-mail is called from the demon,
  >> nnmail-fetched-sources is nil. This means that the 'when
  >> fetching-sources' form where the mail is actually fetched will
  >> not be run.

  Simon> This might work.

  <patch snipped>

Well, yes this fetches new mail, but the group buffer and overview
files are not updated, so I can't see it. To actually see the mail I
still have to press `g'. This is the same problem as with M-g when
using topics. Mail is fetched but not seen.

Of course I can use group levels instead of M-g to fetch just
mail. But I still think this is a bug - or am I missing something? To
get backrround mail fetching work I could write a special version of
g-d-s-news which only fetches mail, I guess. Still don't know what
g-d-s-mail is for as it is though.

After these problems are solved though, remains getting the summary
buffers to be updated *incrementally*. I.e. I want the new message to
appear sorted in place (usually last) when it arrives if the summary
buffer for that group is present. This is something other MUAs do -
pretty standard. Is this possible (I think not), or is this not the
Gnus way - should I use VM if I want this? :-(


Johan
-- 
Johan Parin <Johan.Parin@abc.se>
"Lisp is a programmable programming language" - John Foderaro




  reply	other threads:[~2000-06-07 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tn71z2ihahj.fsf@uab.ericsson.se>
     [not found] ` <iluln0qy2lk.fsf@badis.pdc.kth.se>
     [not found]   ` <tn766ro6zxa.fsf@uab.ericsson.se>
     [not found]     ` <iluhfb6yg3q.fsf@badis.pdc.kth.se>
2000-06-06 20:02       ` IMAP Questions Johan Parin
2000-06-07  0:16         ` Simon Josefsson
2000-06-07 18:35           ` Johan Parin [this message]
2000-06-07 21:38             ` Mail Fetching (was: Re: IMAP Questions) Kai Großjohann
2000-06-08  9:14             ` 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=m3og5dxrtq.fsf_-_@johanspc.abc.se \
    --to=johan.parin@abc.se \
    --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).