From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: [9front] sam input line length limits
Date: Fri, 12 Feb 2021 18:47:02 -0800 [thread overview]
Message-ID: <CAH_zEu70yEVLujRepe321QcqOw=vmCxCLb-3QudD2Zz=B903Ng@mail.gmail.com> (raw)
In-Reply-To: <32B4F44886A8F86854EDDC8FF1699640@5ess.inri.net>
i would be fine bumping the snarf size and making this match. 640k
ought to be enough for anybody.
On Fri, Feb 12, 2021 at 4:48 PM <sl@stanleylieber.com> wrote:
>
> sam.h says:
>
> /*
> * BLOCKSIZE is relatively small to keep memory consumption down.
> */
>
> and:
>
> #define BLOCKSIZE 2048
>
> and:
>
> #define STRSIZE (2*BLOCKSIZE)
>
> is there a compelling reason to keep STRSIZE so small, in this day and
> age?
>
> problem case:
>
> users trying to paste in long articles from websites.
>
> sl
next prev parent reply other threads:[~2021-02-13 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 0:45 sl
2021-02-13 2:47 ` Nick Owens [this message]
2021-02-13 3:43 ` ori
2021-02-13 3:55 ` sl
2021-02-13 16:25 ` Steve Simon
2021-02-13 20:06 ` ori
2021-02-13 20:21 ` Stanley Lieber
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='CAH_zEu70yEVLujRepe321QcqOw=vmCxCLb-3QudD2Zz=B903Ng@mail.gmail.com' \
--to=mischief@offblast.org \
--cc=9front@9front.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 NNTP newsgroup(s).