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

[Dan Christensen <jdc@uwo.ca>]

Dmitry Yaitskov <dimas@home.com> writes:

> Karl Kleinpaste <karl@charcoal.com> writes:
> 
> > 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.
> 
> Sorry, but that's BS. I am not sure what you mean by Gnus' "intended
> UI mechanism". Multi-window, multi-process GUI systems were invented
> to allow the user to switch from one activity/window/etc. to another
> without concern for the "intended UI mechanism"

I agree with Dmitry here.  The behavior of gnus-group-exit (bound to
`q' in the *Group* buffer) suggests that Gnus knows how to handle
active summary buffers.  Why doesn't gnus-group-suspend call
gnus-offer-save-summaries like gnus-group-exit does?

Dan