From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Gnus losing information about what has been read
Date: Thu, 23 Sep 2004 08:32:30 +0200 [thread overview]
Message-ID: <plop87u0tp7awx.fsf@gnu-rox.org> (raw)
In-Reply-To: <m2acvi8bll.fsf@tnuctip.rychter.com>
On 22 sep 2004, Jan Rychter wrote:
> > > > > > "Jonas" == Jonas Steverud <tvrud@bredband.net>
> > > > > > writes:
> Jonas> Jan Rychter <jan@rychter.com> writes:
> > > Am I the only one who sees that?
>
> [...]
>
> Jonas> Besides, are your newsserver reliable? The one I used
> Jonas> before had a habit of reporting all articles new on a
> Jonas> weekly basis (it was a *very* badly admin:ed server run
> Jonas> by my ISP and it was a good thing they closed it down).
> Jonas> I used the caching feature to get around this problem
> Jonas> but I've never used the agent. Do you see the problem
> Jonas> with other newsreaders? Or if you don't use the agent
> Jonas> but reads online for a while?
>
> This happens for me with three news servers, one of them being
> news.gmane.org. I think it only happens if I read news while
> unplugged.
Not only. I have the same problem with the 'J s' command in the
group buffer.
I have clue that there is a problem since, I fetched as usually
this morning my agentized server. When in the train I had tons of
articles (already read), downloaded again and marked as new !!
Note that I suspect this variable
gnus-agent-consider-all-articles to be source of some problems
but with no clue at all.
The docstring is obscur to me:
,----[ C-h v gnus-agent-consider-all-articles RET ]
| gnus-agent-consider-all-articles's value is nil
|
| When non-nil, the agent will let the agent predicate decide
| whether articles need to be downloaded or not, for all articles. When
| nil, the default, the agent will only let the predicate decide
| whether unread articles are downloaded or not. If you enable this,
| groups with large active ranges may open slower and you may also want
| to look into the agent expiry settings to block the expiration of
| read articles as they would just be downloaded again.
|
| You can customize this variable.
|
| Defined in `gnus-agent'.
`----
My problem is that even switching it to t doesn't solve the problem...
--
Xavier Maillard| "Stand Back! I'm a programmer!"
.0. zedek@gnu-rox.orgz|
..0 (+33) 326 770 221 | Webmaster, emacsfr.org
000 PGP : 0x1E028EA5 | Membre de l' APRIL
next prev parent reply other threads:[~2004-09-23 6:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 16:18 Jan Rychter
2004-09-20 23:18 ` Jan Rychter
2004-09-21 6:39 ` Jonas Steverud
2004-09-22 17:20 ` Jan Rychter
2004-09-23 6:32 ` Xavier Maillard [this message]
2004-09-21 8:52 ` Ralf Angeli
2004-09-22 3:12 ` Kevin Greiner
2004-09-22 13:21 ` Ralf Angeli
2004-09-23 0:59 ` Kevin Greiner
2004-09-23 7:59 ` Ralf Angeli
2004-09-23 13:28 ` Kevin Greiner
2004-09-23 14:00 ` Ralf Angeli
2004-09-24 3:52 ` Kevin Greiner
2004-09-24 7:43 ` Ralf Angeli
2004-09-24 12:22 ` Kevin Greiner
2004-09-24 12:32 ` Ralf Angeli
2004-09-24 13:41 ` Kevin Greiner
2004-09-24 16:29 ` Kevin Greiner
2004-09-24 16:30 ` Ralf Angeli
2004-09-23 20:07 ` Jan Rychter
2004-09-24 3:58 ` Kevin Greiner
2004-10-11 20:22 ` Jan Rychter
2004-10-13 3:01 ` Kevin Greiner
2004-10-15 1:12 ` Jan Rychter
2004-09-22 17:13 ` Jan Rychter
2004-09-22 16:29 ` Xavier Maillard
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=plop87u0tp7awx.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).