From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] long lines
Date: Thu, 30 Jan 2014 13:09:31 +0000 [thread overview]
Message-ID: <20140130130931.GB6131@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140030062631.eklhad@comcast.net>
On Thu, Jan 30, 2014 at 06:26:31AM -0500, Karl Dahlke wrote:
> With the latest push, you should be able to substitute in arbitrarily long lines.
> This uses the stringAndString class of functions that you know well.
> There are many cases here, text, input fields on a form,
> renaming files in a directory, replacing one line with many, etc;
> I've tested most of these but not sure if I covered them all.
> They all feed from the same replace string, so should be ok.
> I did test substituting in a line that was 60K long,
> which is beyond our earlier hard limit.
Thanks Karl. I've built this new version and am currently using it to compose this email.
Cheers,
Adam.
prev parent reply other threads:[~2014-01-30 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 11:26 Karl Dahlke
2014-01-30 13:09 ` Adam Thompson [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=20140130130931.GB6131@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).