Re: gnus-group-suspend forgets "readedness" of newly read articles

[Karl Kleinpaste <karl@charcoal.com>]

Dmitry Yaitskov <dimas@home.com> writes:
> There may be a technical reason for what's happening but it is
> still bad UI.

I guess I'd have to ask what you were doing back in *Group*, and
outside an "unresolved" (unaccounted-for?) *Summary*, in the first
place so that the question can even arise.

That is, by the manner in which you were using Gnus, you had subverted
a piece of its intended UI mechanism.  (Enter group from *Group*; read
articles from *Summary*; exit *Summary* properly to induce updates in
*Group*.)  Having successively subverted that, you then complain that
it didn't watch closely enough as you did it.

I see the point you're trying to make, but I see it as akin to someone
complaining that their car's transmission was left on the highway in
pieces as they shifted into reverse while racing.  Sure, you can do
that -- but what were you doing it for, and why is the damage done
considered to be the fault of the car?

About the most "fix" I could see for this would be for
gnus-group-suspend to refuse to do its thing if it saw any
unaccounted-for *Summary* buffers lying around, which would analogize
to a transmission interlock to prevent shifting into reverse.