From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Handling large files with emacs lisp?
Date: Tue, 04 Jun 2013 18:02:35 -0400 [thread overview]
Message-ID: <jwvfvwxwn6j.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CANtbJLEpp8J=Fo4=KiUAEuYk8RGwQF8ce3_TmP1RZZrMAt1+6Q@mail.gmail.com
> Is there a method in emacs lisp to handle large files (hundreds of MB)
> efficiently?
Not really, no. The closest is vlf.el, available from the GNU ELPA.
> Using the BEG and END parameters of `insert-file-contents' however has
> a linear time-dependence on BEG.
I don't know of such a time-dependence. What makes you think so?
Stefan
prev parent reply other threads:[~2013-06-04 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 12:52 Handling large files with emacs lisp? Klaus-Dieter Bauer
2013-06-04 14:46 ` Jambunathan K
2013-06-05 10:47 ` Klaus-Dieter Bauer
2013-06-04 22:02 ` Stefan Monnier [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
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=jwvfvwxwn6j.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).