Gnus development mailing list
 help / color / mirror / Atom feed
From: Alan Shutko <ats@acm.org>
Cc: Justin Sheehy <justin@linus.mitre.org>, ding@gnus.org
Subject: Re: Loss of ticks and marks
Date: 06 Apr 1999 17:02:07 -0500	[thread overview]
Message-ID: <m3iub9s90g.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Alexandre Oliva's message of "06 Apr 1999 18:35:02 -0300"

Alexandre Oliva <oliva@dcc.unicamp.br> writes:

> On Apr  5, 1999, Justin Sheehy <justin@linus.mitre.org> wrote:
> 
> > Entering a large group does in fact have a well-defined interrupt
> > point.
> 
> When I still don't have the faintest idea about how long it will take
> to enter the group.

Especially since the number given at that prompt may have little
relation to the actual number of articles there.

What are the actual problems involved making this operation
interruptable?  (Maybe I just missed an explanation in previous
messages... I'll look.)  It sure seems like a feature people would
like, and I'd say it's worth some effort.

-- 
Alan Shutko <ats@acm.org> - By consent of the corrupted
Memory fault - where am I?


  reply	other threads:[~1999-04-06 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-21  7:59 Alexandre Oliva
1999-03-28 16:41 ` Lars Magne Ingebrigtsen
1999-03-29  0:56   ` Alexandre Oliva
1999-04-02 13:53     ` Lars Magne Ingebrigtsen
1999-04-04 10:57       ` Alexandre Oliva
1999-04-05 15:28         ` Justin Sheehy
1999-04-05 21:24           ` Alexandre Oliva
1999-04-05 21:34             ` Justin Sheehy
1999-04-05 22:08               ` Dmitry Yaitskov
1999-04-06 21:35               ` Alexandre Oliva
1999-04-06 22:02                 ` Alan Shutko [this message]
1999-04-13  7:08           ` Hrvoje Niksic
1999-04-17  6:20         ` Lars Magne Ingebrigtsen
1999-04-17 20:27           ` Alexandre Oliva

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=m3iub9s90g.fsf@hubert.wuh.wustl.edu \
    --to=ats@acm.org \
    --cc=ding@gnus.org \
    --cc=justin@linus.mitre.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).