Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Richards <cjr@netpliance.net>
Cc: Chris Richards <cjr@netpliance.net>, ding@gnus.org
Subject: Re: gnus-summary-mail-forward for more messages?
Date: 18 Apr 2000 10:26:16 -0500	[thread overview]
Message-ID: <6eg0sjtopz.fsf@sloth.netpliance.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "18 Apr 2000 10:06:15 +0200"

I have digested groups of that size before.  It was something with
that 30th message.  Unfortunately, I was in a hurry to compile
information for someone and could not explore the problem fully.

Cheers,
cjr

-- 
A train stops at a train station.  A bus stops at a bus station.  On
my desk I have a workstation...

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Chris Richards <cjr@netpliance.net> writes:
> 
> > This doesn't always work.  I had 677 messages marked to digest and it
> > died around #30.  Vague yes, but it died nonetheless.  The 30-some-odd
> > messages that it processed had the process mark removed.
> 
> Can you say M-x toggle-debug-on-error RET (or set the variable
> debug-on-error to t if using XEmacs), then repeat the problem?  I
> don't think anybody has ever testing digesting such a large number of
> messages. 
> 
> kai
> -- 
> Beware of flying birch trees.



  reply	other threads:[~2000-04-18 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-17 17:09 Pavel Janik ml.
2000-04-17 18:41 ` Kevin Falcone
2000-04-18  3:54   ` Chris Richards
2000-04-18  8:06     ` Kai Großjohann
2000-04-18 15:26       ` Chris Richards [this message]
2000-04-30 19:53   ` Mike Fabian
2000-08-10 20:55     ` Lars Magne Ingebrigtsen
2000-08-11  6:40       ` Mike Fabian
2000-08-11 13:30         ` ShengHuo ZHU

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=6eg0sjtopz.fsf@sloth.netpliance.net \
    --to=cjr@netpliance.net \
    --cc=ding@gnus.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).