From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: "maximum buffer size exceeded" error
Date: Mon, 03 Oct 2005 23:09:23 -0400 [thread overview]
Message-ID: <874q7yhtf6.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.8889.1127859685.20277.help-gnu-emacs@gnu.org
> I am trying to work on text files in excess of 180 Mb. When I try to open
> the file I get the above response (in quotes).
> Is there a way to set the maximum buffer size so that I can open these
> bigger files?
In 32bit systems, It's 128MB on Emacs-21. It'll be 256MB on Emacs-22.
It can be made 512MB fairly easily (patch not provided, tho).
But it can also be made insanely large by recompiling on a 64bit system.
This "insanely large" is the theory. Practice will probably bump into bugs
when crossing the 2GB limit.
Stefan
next parent reply other threads:[~2005-10-04 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8889.1127859685.20277.help-gnu-emacs@gnu.org>
2005-10-04 3:09 ` Stefan Monnier [this message]
2005-09-27 21:58 "maximum buffer size exceeded" error Dan Simon
2005-09-27 22:50 ` Peter Dyballa
2005-09-28 16:25 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874q7yhtf6.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).