Gnus development mailing list
 help / color / mirror / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: GNUS mailing list <ding@gnus.org>
Subject: Re: display-time, mail-icon and POP3 mailboxes
Date: 10 Feb 2002 20:57:13 +0100	[thread overview]
Message-ID: <5xn0yhrtye.fsf__21227.8342842639$1042212400@kfs2.cua.dk> (raw)
In-Reply-To: <m3pu3dqizu.fsf@Janik.cz>

Pavel@Janik.cz (Pavel Janík) writes:

>    From: storm@cua.dk (Kim F. Storm)
>    Date: 09 Feb 2002 00:14:55 +0100
> 
>    > I think it should at least be able to use the existing gnus and/or
>    > rmail settings (they cannot be that hard to use).
>    > You can then add extra mailboxes to check specifically.
>    > 
>    > What about these options:
>    >  - display-time-pop3-check-rmail  (nil/t, default t)
>    >  - display-time-pop3-check-gnus   (nil/t, default t)
>    >  - display-time-pop3-mail-boxes   (alist (server.passwd), default ())
> 
> Hmm, when I think about it - it would be better if those mail programs like
> RMAIL and Gnus could tells us alone if there is any new mail. Syntax of
> Gnus' mail-sources variable is pretty easy, but Gnus also support IMAP
> etc. and we should not duplicate code in display-time. What do you think?

I agree.  It seems to be the right approach for such packages to have
a hook function for display-time to check for unread mail (using whatever
method those packages support for retrieving mail).

> 
>    > With the pop3 sample code I posted some time ago, there is one serious
>    > problem: If emacs cannot connect to the pop3 server, it may hang (no
>    > user interaction) until the connect times out.  That is not
>    > satisfactory!
>    > 
>    > I don't know if this is relevant for your code (sorry, but I haven't
>    > had time to look at the code you sent me).
> 
> The same applies to pop3.el from Gnus.

In my experience [based on my own pop3 hacks], this is really, really
annoying (since the poll runs through a timer)!!!

If we want to support this in general, we must implement an async
version of open-network-stream (or add an optional arg to it to make
it async - that arg could be a function which is called when the
connection has been opened.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk




  reply	other threads:[~2002-02-10 19:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3ofj1fwhj.fsf@Janik.cz>
     [not found] ` <200202081357.g18Dvfw05454@aztec.santafe.edu>
     [not found]   ` <m3bsezk837.fsf@Janik.cz>
     [not found]     ` <5x1yfva7m8.fsf@kfs2.cua.dk>
2002-02-10 18:39       ` Pavel Janík
2002-02-10 19:57         ` Kim F. Storm [this message]
     [not found]         ` <5xn0yhrtye.fsf@kfs2.cua.dk>
2002-02-11 18:48           ` Richard Stallman
2002-02-11 23:31             ` Kim F. Storm
     [not found]             ` <a49p7s$657$1@quimby2.netfonds.no>
2002-02-12 16:25               ` Jan Vroonhof
     [not found]             ` <5x3d07iojn.fsf@kfs2.cua.dk>
2002-02-12 16:32               ` Paul Jarc
     [not found]               ` <m3u1sm4q4f.fsf@multivac.cwru.edu>
2002-02-13  0:27                 ` Kim F. Storm
     [not found]                 ` <5x4rkmfcp8.fsf@kfs2.cua.dk>
2002-02-14  3:12                   ` Richard Stallman
2002-02-14  9:41                     ` Kim F. Storm
     [not found]                     ` <5xlmdwe6ym.fsf@kfs2.cua.dk>
2002-02-15 10:36                       ` Richard Stallman
2002-02-13 15:38               ` Richard Stallman
2002-02-13 22:13                 ` Kim F. Storm
     [not found]                 ` <5x3d0558tf.fsf@kfs2.cua.dk>
2002-02-15 10:37                   ` Richard Stallman

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='5xn0yhrtye.fsf__21227.8342842639$1042212400@kfs2.cua.dk' \
    --to=storm@cua.dk \
    --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).