From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Maximum buffer size exceeded
Date: 05 May 2004 13:22:25 +0200 [thread overview]
Message-ID: <uvfjbw232.fsf@gnu.org> (raw)
In-Reply-To: <lzllk7to73.fsf@tristan.br-automation.de> (message from Marco Gidde on 05 May 2004 07:53:04 +0200)
> From: Marco Gidde <marco.gidde@tiscali.de>
> Newsgroups: gnu.emacs.help
> Date: 05 May 2004 07:53:04 +0200
>
> I was in the same situation a few days ago, a large file with more
> than 200MB. It's sad, but vim did the job without complaining.
Why ``sad''? Every editor has its breaking point wrt file sizes; I
imagine vim would break somewhere near 2GB, if not before that.
OTOH, why would someone need to load such a huge file into an
interactive editor like Emacs or vim? Sed sounds like a perfect tool
for the job (faster, too).
In other words, there's the best tool for every job, and Emacs (nor
vim) is not the one for this job.
next prev parent reply other threads:[~2004-05-05 11:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3364.1083718441.1061.help-gnu-emacs@gnu.org>
2004-05-05 2:00 ` Maximum buffer size exceeded Kin Cho
2004-05-05 3:26 ` Harish Narayanan
[not found] ` <mailman.3382.1083727713.1061.help-gnu-emacs@gnu.org>
2004-05-05 5:18 ` Kin Cho
2004-05-05 9:36 ` Thien-Thi Nguyen
2004-05-05 5:53 ` Marco Gidde
2004-05-05 11:22 ` Eli Zaretskii [this message]
[not found] ` <mailman.3431.1083752452.1061.help-gnu-emacs@gnu.org>
2004-05-05 11:45 ` Marco Gidde
2004-05-06 6:26 ` Eli Zaretskii
[not found] ` <mailman.3625.1083821602.1061.help-gnu-emacs@gnu.org>
2004-05-06 8:21 ` Marco Gidde
2004-05-06 12:12 ` Thien-Thi Nguyen
2004-05-05 15:56 ` Miles Bader
2004-05-05 19:35 ` Stefan Monnier
2004-05-06 6:30 ` Eli Zaretskii
2004-05-05 17:16 ` Michael Welsh Duggan
[not found] ` <mailman.3511.1083777609.1061.help-gnu-emacs@gnu.org>
2004-05-05 19:37 ` upro
2004-05-05 5:50 ` Matthieu Moy
2004-05-05 19:31 ` Stefan Monnier
2007-09-02 6:44 maximum " Daniel C. Bastos
2007-09-02 11:59 ` Emilio Lopes
2007-09-02 21:39 ` Daniel C. Bastos
2007-09-03 8:18 ` Tim X
2007-09-03 12:52 ` Daniel C. Bastos
2007-09-03 19:24 ` Eli Zaretskii
2007-09-04 11:07 ` Johan Bockgård
[not found] ` <mailman.254.1188847491.18990.help-gnu-emacs@gnu.org>
2007-09-04 12:13 ` Giorgos Keramidas
2007-09-04 14:48 ` Peter Dyballa
[not found] ` <mailman.308.1188917334.18990.help-gnu-emacs@gnu.org>
2007-09-04 18:13 ` Emilio Lopes
2007-09-04 19:10 ` Giorgos Keramidas
2007-09-04 20:22 ` Eli Zaretskii
2007-09-05 12:37 ` Kim F. Storm
2007-09-05 15:00 ` Stefan Monnier
2007-09-05 15:14 ` Jason Rumney
2007-09-05 16:08 ` Stefan Monnier
2007-09-06 4:59 ` Richard Stallman
2007-09-06 5:44 ` David Kastrup
2007-09-02 19:24 ` Eli Zaretskii
2007-09-03 23:25 ` Glenn Morris
2007-09-04 8:20 ` Tim X
2007-09-04 17:31 ` Glenn Morris
2007-09-05 8:20 ` Tim X
2007-09-04 17:53 ` Daniel C. Bastos
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 0:52 Maximum " Harish Narayanan
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=uvfjbw232.fsf@gnu.org \
--to=eliz@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.
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.