From: Peter Graves <peter@ar...> - 2002-10-05 18:55:26
http://armedbear.org/j.zip (source and documentation)
http://armedbear.org/j-jar.zip (just j.jar)
The shellCommand output buffer now enforces an output limit (1000
lines by default).
What this means is, if the actual output exceeds 1000 lines, only the
most recent 1000 lines at any given moment are kept in the buffer;
earlier lines are discarded.
The 1000-line default is probably a tad small. You can change it by
specifying a different value in ~/.j/prefs, e.g.:
shellOutputLimit = 5000
If you set shellOutputLimit to zero, no output limit is enforced.
The shellOutputLimit property has been used for quite a while to
specify the output limit for shell buffers (which are a different
thing entirely). It seemed reasonable to use the same limit for the
shellCommand output buffer. Feel free to complain if you think there
should be two separate properties.
I've confirmed that nothing untoward happens if you run a shellCommand
that generates a whole lot of character output, but no line breaks, a
situation which circumvents the shellOutputLimit mechanism. You should
still be able to close the output buffer by hitting Escape or Ctrl W,
which will kill the underlying process, and things will return to
In other news, I've added a bit of code to trap OutOfMemoryErrors in a
couple of situations, so starting with this snapshot, j is much more
likely to survive if you attempt to open a file that's too big to fit
in memory (for example). You should now get an error message in that
situation, and j should be able to carry on.
Thanks for your support.