Possible small bug in agent

Possible small bug in agent

[Harry Putnam]

This little aggravation has happened here a number of times:

I have  `gnus-agent-handle-level 3' so I can set some groups above that
and hopefully agent will ignore them.  

The groups mentioned below are on my native server so this is not a
`foreign server' situation.

I keep two groups set to level 4 and agent dutifully ignores them
except in this one circumstance.

If, while in `unplugged' mode I happen to hit `g' on one of those
groups, the number of unread immediately goes to zero, as gnus says
something like `no more unread news'.

Once I've told the agent to `ignore' groups above 3, it seems I should
be able to expect the agent to in fact, ignore them, and not change
there readedness marks, but give me a message something like:

"this group is not under agent management"

Re: Possible small bug in agent

[ShengHuo ZHU]

Harry Putnam <reader@newsguy.com> writes:

> This little aggravation has happened here a number of times:
> 
> I have  `gnus-agent-handle-level 3' so I can set some groups above that
> and hopefully agent will ignore them.  
> 
> The groups mentioned below are on my native server so this is not a
> `foreign server' situation.
> 
> I keep two groups set to level 4 and agent dutifully ignores them
> except in this one circumstance.
> 
> If, while in `unplugged' mode I happen to hit `g' on one of those
> groups, the number of unread immediately goes to zero, as gnus says
> something like `no more unread news'.
> 
> Once I've told the agent to `ignore' groups above 3, it seems I should
> be able to expect the agent to in fact, ignore them, and not change
> there readedness marks, but give me a message something like:
> 
> "this group is not under agent management"

gnus-agent-handle-level is only used in gnus-agent-fetch-session(J
s). It doesn't prohibit a user to fetch articles of groups above the
level(J u), so the groups are still under agent management.

The number of unread is changed because the .overview file in nnagent
is not updated.  It happens when you enter a group (even below
g-a-h-level) without having fetched the headers, e.g. `J j g J j'.

Possibly, it is not a bug because "The Gnus Agent doesn't seem to work
like most other offline newsreaders."

ShengHuo

Re: Possible small bug in agent

[Harry Putnam]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> gnus-agent-handle-level is only used in gnus-agent-fetch-session(J
> s). It doesn't prohibit a user to fetch articles of groups above the
> level(J u), so the groups are still under agent management.
> 
> The number of unread is changed because the .overview file in nnagent
> is not updated.  It happens when you enter a group (even below
> g-a-h-level) without having fetched the headers, e.g. `J j g J j'.

Thanks... at least now I understand the mechanism involved.  Maybe it
wouldn't be so hard to write somekind of hook called by `g' that
notices if gnus is in agent mode and notices if g-a-h-level is in force.

And says something like.... "Wait! You are `unplugged'. Don't open
this group unless you don't mind loosing all track of readedness.
Be warned, the mighty `AGENT' manages all groups under HIS servers"

> 
> Possibly, it is not a bug because "The Gnus Agent doesn't seem to work
> like most other offline newsreaders."

He he... Possibly it is a well thought out feature, the work of a
savant, because "The Gnus Agent doesn't seem to work like *ANY* other
offline reader."