From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: gnus-group-suspend forgets "readedness" of newly read articles
Date: 07 Feb 2001 13:59:44 -0500 [thread overview]
Message-ID: <m3g0hqco95.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Karl Kleinpaste's message of "07 Feb 2001 13:50:46 -0500"
Karl Kleinpaste <karl@charcoal.com> writes:
> 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.
Is there any reason the *Group* buffer couldn't be updated
continuously? Instead of batching things together in *Summary* and
then handing a big set of changes to *Group* (and backends), why not
let *Group* and backends be immediately notified of any changes?
paul
next prev parent reply other threads:[~2001-02-07 18:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 16:57 Dmitry Yaitskov
2001-02-07 17:03 ` Karl Kleinpaste
2001-02-07 17:29 ` Toby Speight
2001-02-07 18:02 ` Dmitry Yaitskov
2001-02-07 18:03 ` Dmitry Yaitskov
2001-02-07 18:50 ` Karl Kleinpaste
2001-02-07 18:59 ` Paul Jarc [this message]
2001-02-07 19:30 ` Dmitry Yaitskov
2001-02-08 1:17 ` Dan Christensen
2001-02-08 2:19 ` Karl Kleinpaste
2001-02-11 15:03 ` ShengHuo ZHU
2001-02-08 0:08 ` Andreas Fuchs
2001-02-08 15:43 ` Kai Großjohann
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=m3g0hqco95.fsf@multivac.student.cwru.edu \
--to=prj@po.cwru.edu \
/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).