sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Bengt Kleberg <>
Subject: Re: Input buffer limit???
Date: Wed, 5 Apr 2000 06:51:37 -0400	[thread overview]
Message-ID: <> (raw)

> From: Jim Crigler <>

> The other day I was typing in some text via the "sam"
> (command) window and after a few tens of lines (don't
> know how many; sorry), I suddenly got a message in the
> command window like "?out of buffer memory"


I ahve tried various combinations. Many lines work fine, I have > 60 lines with
> 1500 characters after an a command.
But, 1 long line does have problem after 512 characters. It appears that sam can only send 512
bytes to samterm.

As a workaround, could you limit your lines to 512 characters and then join them together after they have arrived
in the file?
Presumably it should be possible to change this limit if it is a problem...

Best Wishes, Bengt
Everything aforementioned should be regarded as totally private
opinions, and nothing else.
``His great strength is that he is uncompromising. It would make
him physically ill to think of programming in C++.''

             reply	other threads:[~2000-04-12  4:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-05 10:51 Bengt Kleberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-31 15:47 Jim Crigler

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).