Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@ms.com>
Subject: [bug] gnus-start-date-timer problems.
Date: 08 Oct 1998 14:14:39 -400	[thread overview]
Message-ID: <vgvsogyudio.fsf@ms.com> (raw)

Hi-

I have gnus-single-article-buffer set to nil, and recently upgraded to 
pgnus.

Anyway, I think gnus-start-date-timer is quote cool.  However, it does 
not play well with multiple article buffers.

Here is how to reproduce the problem:

1. Create two frames, side by side, each showing the *Group* buffer.

2. In the first frame, select a group, and open an article.  You will
   see the X-Sent slowing changing correctly.

3. Go to the second frame.  As soon as you leave the first frame, the
   X-Sent stops changing.  This is my first problem, though it has
   nothing to do with gnus-single-article-buffer.

4. Now select a group, and open an article.  You will see the second
   article's X-Sent change correctly.

5. Change focus back to the first frame in the first *Summary* buffer.
   The X-Sent in the second article will stop, and the X-Sent in the
   first article will change to what the second article should have.

The first problem is that `article-update-date-lapsed' is checking
"(get-buffer-window gnus-article-buffer)", when it should probably be
using "(get-buffer-window gnus-article-buffer 'visible)".

The second problem is more problematic.  There are more than one
article buffers, but there is only one gnus-article-buffer.  Maybe
have a list of them, and any daemons that work on articles mapcar the
list.

-- 
Colin


             reply	other threads:[~1998-10-08 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-08 18:14 Colin Rafferty [this message]
1998-10-10 22:57 ` Lars Magne Ingebrigtsen

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=vgvsogyudio.fsf@ms.com \
    --to=craffert@ms.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).