From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Dmitry Antipov <antipov@mvista.com>, emacs-devel@gnu.org
Subject: Re: --with-wide-int
Date: Mon, 28 Nov 2011 23:35:51 -0800 [thread overview]
Message-ID: <4ED48B57.20304@cs.ucla.edu> (raw)
In-Reply-To: <jwvwrakchxw.fsf-monnier+emacs@gnu.org>
On 11/28/11 08:52, Stefan Monnier wrote:
> I'd be surprised if non-simple edits (e.g. insertion of enough text to
> overflow the gap and force a reallocation) works at all.
It'd have to be a bit more complex than that.
(insert-char ?\n (1+ (gap-size)))
worked just fine on that nearly-2GB file,
and I later typed additional randomish text without
trouble (this is on 32-bit Emacs configured --with-wide-int).
One can easily come up with the more-complex edits
that will make Emacs run out of memory editing that file,
but these problems are not unknown with a 500 MB limit as well.
Users who skate that close to memory's edge
already understand that there are limits. It's nicer
to have the edge be at 2 GB rather than 500 MB.
I typically want just read-only access to large text
files, and support for more-complex edits isn't
so high a priority.
prev parent reply other threads:[~2011-11-29 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 2:15 immediate strings Dmitry Antipov
2011-11-26 7:56 ` Andreas Schwab
2011-11-26 8:05 ` Paul Eggert
2011-11-26 10:03 ` Eli Zaretskii
2011-11-26 14:28 ` Stefan Monnier
2011-11-26 14:30 ` Dmitry Antipov
2011-11-26 21:13 ` Paul Eggert
2011-11-28 4:19 ` --with-wide-int Stefan Monnier
2011-11-28 7:56 ` --with-wide-int Paul Eggert
2011-11-28 16:52 ` --with-wide-int Stefan Monnier
2011-11-28 18:04 ` --with-wide-int Dan Nicolaescu
2011-11-28 18:34 ` --with-wide-int Eli Zaretskii
2011-11-28 19:35 ` --with-wide-int Stefan Monnier
2011-11-29 4:26 ` --with-wide-int Stephen J. Turnbull
2011-11-29 7:35 ` Paul Eggert [this message]
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=4ED48B57.20304@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=antipov@mvista.com \
--cc=emacs-devel@gnu.org \
--cc=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.
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.