all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: nnfolder and large-file-warning-threshold
Date: Wed, 08 Sep 2004 20:37:10 +0200	[thread overview]
Message-ID: <v9zn40vc89.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9acwhu3yz.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 26 Aug 2004 20:52:20 +0200")

On Thu, Aug 26 2004, Reiner Steib wrote:

> when using Gnus with the nnfolder[1] back end which is used by default
> for sent messages, people get...
>
> | File sent-mail is large (11MB), really open? (y or n) 
>
> ... when sending a mail.
>
> This is caused by the variable `large-file-warning-threshold' that has
> been introduced in Emacs 21.3.50.
>
> 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'?

No opinions on that?  Could someone explain the reason for
`large-file-warning-threshold'?

> [1] The nnfolder back end is a "one file per group" back end.
>     I.e. the file may grow quite fast when a user stores sent
>     attachments there.
>
> [2] `nnheader-find-file-noselect' (used in `nnfolder-read-folder',
>     `nnmbox-read-mbox', `nnbabyl-read-mbox', ...)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 18:52 nnfolder and large-file-warning-threshold Reiner Steib
2004-09-08 18:37 ` Reiner Steib [this message]
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
     [not found] ` <87oekxg1fl.fsf@koldfront.dk>
2004-09-08 18:37   ` 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=v9zn40vc89.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=Reiner.Steib@gmx.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.