Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: nnfolder and large-file-warning-threshold
Date: Wed, 08 Sep 2004 21:08:30 +0200	[thread overview]
Message-ID: <873c1s1sup.fsf@koldfront.dk> (raw)
In-Reply-To: <v9y8jkvc86.fsf@marauder.physik.uni-ulm.de>

On Wed, 08 Sep 2004 20:37:13 +0200, Reiner wrote:

> On Thu, Aug 26 2004, Adam Sjøgren wrote:

>> On Thu, 26 Aug 2004 20:52:20 +0200, Reiner wrote:

>>> Should we bind `large-file-warning-threshold' to a larger value
>>> (or nil) in the relevant Gnus functions[2] or would it be better
>>> to increase the default value of `large-file-warning-threshold'?

>> How about defaulting to nnml: instead of nnfolder: for the archive? 
>> Any reason not to?

> This won't be a remedy for people using large nnfolder
> archives/groups. But I certainly would object to such a change. I
> don't know if it can be done in a backward compatible way.

You're right, of course, it won't help people in that situation - I
was merely thinking of the default for people in the future, so it
would be less easy to get into in the first place.


  Best regards,

-- 
 "Who ees thees Kählveen?"                                    Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2004-09-08 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 18:52 Reiner Steib
2004-08-26 19:10 ` Adam Sjøgren
2004-09-08 18:37   ` Reiner Steib
2004-09-08 19:08     ` Adam Sjøgren [this message]
2004-09-08 18:37 ` Reiner Steib
2004-09-08 21:36   ` Stefan
2004-09-08 23:26     ` Kenichi Handa
2004-09-08 23:31       ` Stefan Monnier
2004-09-08 23:34         ` Stefan Monnier
2004-09-08 23:52         ` Kenichi Handa
2005-02-24 20:30     ` Reiner Steib

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=873c1s1sup.fsf@koldfront.dk \
    --to=asjo@koldfront.dk \
    /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).