From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] 100 million lines
Date: Fri, 31 Jan 2014 11:32:49 -0500 [thread overview]
Message-ID: <20140031113249.eklhad@comcast.net> (raw)
Ok edbrowse can now manage 100 million lines of text.
It was just some constants in eb.h.
I didn't think it would be that easy, but there it is.
However, in the words of Oklahoma, she's gone about as fer as she can go.
I'm confident, but didn't est it;
I suppose I should create a file with 11 million newlines and edit it.
Karl Dahlke
reply other threads:[~2014-01-31 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140031113249.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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 NNTP newsgroup(s).