From: Timur Aydin <timuraydin@ttnet.net.tr>
Subject: more info on gnus missing the fact that there are new messages
Date: Sun, 12 Jan 2003 16:00:04 +0200 [thread overview]
Message-ID: <m3el7io4d7.fsf@ttnet.net.tr> (raw)
Hi,
I am using Oort 0.11 from CVS (retrieved today) and gnus doesn't seem
to handle the new messages count properly. Here is the minimal setup
that I do to duplicate the problem:
1) I have installed emacs 21.2 from the Red Hat 8.0 RPM files.
2) Then I have renamed the /usr/share/emacs/21.2/lisp/gnus to
gnus-21.2.
3) I have retrieved oort from CVS, did ./configure and specified the
lisp path as /usr/share/emacs/21.2/lisp/gnus and the etc path as
/usr/share/emacs/21.2/etc. Then I did make and make install.
4) Then deleted the News/ and Mail/ directories and all .newsrc*
files.
5) I ran emacs and then M-x gnus-no-server.
6) I subscribed to gnu.emacs.gnus.
7) I restarted gnus and did a catch up on the gnu.emacs.gnus group (0
new articles). Then in the server window, I activated agent support
using J a.
8) Then I restarted gnus and hit "g" in the group buffer. As expected,
no new messages. I then entered the group and retrieved 500
articles. I left the group and hit "g" again. This time, gnus told
me there are 197 new messages!
9) I restarted gnus again, hit "g" in the group buffer. No new
messages. I then entered gnu.emacs.gnus and retrieved 500
messages. Because the messages are cached in the agent, this
completed insstantly. I left the group and hit "g" again. This
time, gnus told me there are 205 new messages!
10) I repeat the above again and now gnus tell me there are 207 new
messages !
Can anybody tell me what is happening? I am using the giganews news
service over a dialup line.
My general impression is that gnus is not aware of the most recently
added messages. If I am away for several days and enter gnus and hit g
in the group buffer, gnus shows new messages, but the count is far
less than the actual number of new messages.
Just to see whether there is a problem with the news server, I have
installed "pan" (pimp ass newsreader) and the server seems to be
fine.
Here is my .gnus
(setq user-mail-address "timuraydin@ttnet.net.tr")
(setq user-full-name "Timur Aydin")
(setq gnus-select-method '(nntp "news-east.giganews.com"))
I can also provide the relevant files in News/ or .newsrc.eld, if
necessary...
--
Timur Aydin
next reply other threads:[~2003-01-12 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 14:00 Timur Aydin [this message]
[not found] ` <m3n0m65uxf.fsf@quimbies.gnus.org>
[not found] ` <m3lm1qo345.fsf@ttnet.net.tr>
[not found] ` <m3el7i5tq8.fsf@quimbies.gnus.org>
[not found] ` <m3heces8ab.fsf@ttnet.net.tr>
[not found] ` <m38yxq5r6p.fsf@quimbies.gnus.org>
[not found] ` <m3el7is7hb.fsf@ttnet.net.tr>
[not found] ` <m365su5pl7.fsf@quimbies.gnus.org>
[not found] ` <pan.2003.01.12.16.28.38.348639@ttnet.net.tr>
[not found] ` <m3y95q48ut.fsf@quimbies.gnus.org>
[not found] ` <8765sunvbq.fsf@unix.home>
[not found] ` <m3d6n2450g.fsf@quimbies.gnus.org>
[not found] ` <87d6n2yxzo.fsf@unix.home>
[not found] ` <84r8bitapo.fsf@lucy.is.informatik.uni-duisburg.de>
2003-01-12 20:00 ` Vasily Korytov
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=m3el7io4d7.fsf@ttnet.net.tr \
--to=timuraydin@ttnet.net.tr \
/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).