Gnus development mailing list
 help / color / mirror / Atom feed
From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: Loss of ticks and marks
Date: 05 Apr 1999 18:08:04 -0400	[thread overview]
Message-ID: <u7lrq7mbf.fsf@home.com> (raw)
In-Reply-To: Justin Sheehy's message of "05 Apr 1999 17:34:36 -0400"

Justin Sheehy <justin@linus.mitre.org> wrote:

> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
> 
> > But functions that may take a long time to run, such as entering a
> > large group, should have well-defined interrupt points or be safe to
> > interrupt, otherwise people may lose e-mail like I have :-(
> 
> Entering a large group does in fact have a well-defined interrupt
> point.  You just explained the exact reason why Gnus asks you for
> confirmation when selecting a large group.
> 
> If you confirm this, or set gnus-large-newsgroup to nil, then you are
> intentionally allowing the very well defined interrupt-safe time to
> pass.  If you do that, then you should let the subsequent code finish
> nicely.

BTW. Wouldn't it be nice to be able to set gnus-large-newsgroup per
group? Or is it already possible? (I once tried to set it in group
parameters, but it didn't work.)

-- 
Cheers,
-Dima.



  reply	other threads:[~1999-04-05 22:08 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 [this message]
1999-04-06 21:35               ` Alexandre Oliva
1999-04-06 22:02                 ` Alan Shutko
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=u7lrq7mbf.fsf@home.com \
    --to=dimas@home.com \
    /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).