From: Kenichi Handa <handa@m17n.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: nnfolder and large-file-warning-threshold
Date: Thu, 9 Sep 2004 08:26:48 +0900 (JST) [thread overview]
Message-ID: <200409082326.IAA28541@etlken.m17n.org> (raw)
In-Reply-To: <m1pt4wfntr.fsf-monnier+emacs@gnu.org> (message from Stefan on Wed, 08 Sep 2004 17:36:57 -0400)
In article <m1pt4wfntr.fsf-monnier+emacs@gnu.org>, Stefan <monnier@iro.umontreal.ca> writes:
>> No opinions on that? Could someone explain the reason for
>> `large-file-warning-threshold'?
> Emacs doesn't handle large files very well in my experience (particularly if
> they're not read in as binary in fundamental mode), so I've added this
> warning in case you open a very large file without intending to.
Do you mean that you find a bug on decoding a very large
file, or that the decoding is just very slow?
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2004-09-08 23:26 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
2004-09-08 18:37 ` Reiner Steib
2004-09-08 21:36 ` Stefan
2004-09-08 23:26 ` Kenichi Handa [this message]
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=200409082326.IAA28541@etlken.m17n.org \
--to=handa@m17n.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).