From: "Andreas Röhler" <andreas.roehler@online.de>
To: help-gnu-emacs@gnu.org
Cc: Xah Lee s <xah@xahlee.org>, Sven Joachim <svenjoac@gmx.de>
Subject: Re: opening large files (few hundred meg)
Date: Mon, 28 Jan 2008 21:36:50 +0100 [thread overview]
Message-ID: <200801282136.50775.andreas.roehler@online.de> (raw)
In-Reply-To: <uwsptkaqs.fsf@gnu.org>
Am Montag, 28. Januar 2008 20:31 schrieb Eli Zaretskii:
> > From: Sven Joachim <svenjoac@gmx.de>
> > Date: Mon, 28 Jan 2008 19:05:41 +0100
> >
> > > • How can i increase the limit?
> >
> > Use a 64-bit system.
>
> Yes, that's the only practical way, sans splitting the file outside of
> Emacs.
>
> > > • is there a general solution to work with files (elisp) without
> > > actually loading the whole file?
> >
> > Not really, since visiting a file reads all of it into an Emacs buffer.
>
> The problem is not with the buffer size per se, it's with the fact
> that Emacs needs to be able to address each byte of the file's text
> with an Emacs integer data type, which is 29 bit wide on 32-bit
> machines.
>
What about a large-text-mode: sed reads chunks of text
in, one by one, letting Emacs forget the rest. Than
only the line-no matters, sent to sed.
Andreas Röhler
next prev parent reply other threads:[~2008-01-28 20:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 17:35 opening large files (few hundred meg) Xah Lee
2008-01-28 18:05 ` Sven Joachim
2008-01-28 19:31 ` Eli Zaretskii
2008-01-28 20:36 ` Andreas Röhler [this message]
[not found] ` <mailman.6652.1201552566.18990.help-gnu-emacs@gnu.org>
2008-01-28 21:50 ` Jason Rumney
2008-01-29 7:07 ` Andreas Röhler
2008-01-29 7:20 ` Thierry Volpiatto
[not found] ` <mailman.6666.1201591238.18990.help-gnu-emacs@gnu.org>
2008-01-29 9:08 ` Tim X
2008-01-29 16:34 ` Xah Lee
2008-01-29 19:06 ` Tom Tromey
2008-01-29 20:44 ` Eli Zaretskii
[not found] ` <mailman.6705.1201639469.18990.help-gnu-emacs@gnu.org>
2008-01-30 20:01 ` Stefan Monnier
2008-01-30 22:04 ` Eli Zaretskii
2008-01-29 22:10 ` Jason Rumney
2008-01-30 17:08 ` Joel J. Adamson
2008-01-31 5:57 ` Tim X
2008-01-31 15:35 ` Stefan Monnier
2008-02-08 11:25 ` Giacomo Boffi
2008-02-06 1:47 ` Samuel Karl Peterson
2008-01-29 14:52 ` Joel J. Adamson
2008-01-30 14:55 ` Stefan Monnier
2008-02-06 16:42 ` Mathias Dahl
2008-02-06 16:55 ` Mathias Dahl
2008-01-29 10:43 ` Johan Bockgård
2008-01-29 15:35 ` Andreas Röhler
2008-02-06 1:25 ` Samuel Karl Peterson
2008-02-17 16:01 ` Kevin Rodgers
2008-01-29 16:33 ` Ted Zlatanov
[not found] ` <mailman.6646.1201548710.18990.help-gnu-emacs@gnu.org>
2008-01-30 15:12 ` Stefan Monnier
2008-01-30 16:55 ` Sven Joachim
2008-01-30 21:53 ` Stefan Monnier
2008-01-31 22:55 ` Ilya Zakharevich
[not found] ` <200801312255.m0VMt701019096@powdermilk.math.berkeley.edu>
2008-02-01 11:04 ` Eli Zaretskii
[not found] ` <mailman.6836.1201863892.18990.help-gnu-emacs@gnu.org>
2008-02-01 22:26 ` Ilya Zakharevich
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=200801282136.50775.andreas.roehler@online.de \
--to=andreas.roehler@online.de \
--cc=help-gnu-emacs@gnu.org \
--cc=svenjoac@gmx.de \
--cc=xah@xahlee.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.
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.