Skip to content

Commit 56b8913

Browse files
cs7.4 doc update
1 parent 9d1e3b1 commit 56b8913

File tree

1 file changed

+11
-12
lines changed

1 file changed

+11
-12
lines changed

WIKI/ChatScript-Command-Line-Parameters.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
# ChatScript Command Line Parameters
2-
3-
> Copyright Bruce Wilcox, [email protected] brilligunderstanding.com
4-
5-
<br>Revision 4/24/2017 cs7.4
2+
Copyright Bruce Wilcox, [email protected] www.brilligunderstanding.com<br>
3+
Revision 4/24/2017 cs7.4
64

75
# Command Line Parameters
86

@@ -68,14 +66,15 @@ to have enough normal working room.
6866
| option | description
6967
|--------------------|-----------------------------------------------------------------------------
7068
| `output=nnn` | limits output line length for a bot to that amount (forcing crnl as needed). 0 is unlimited.
71-
| `outputsize=80000` | is the maximum output that can be shipped by a volley from the bot without getting truncated.
72-
Actually the value is somewhat less, because routines generating partial data for later incorporation into
73-
the output also use the buffer and need some usually small amount of clearance. You can find out how close
74-
you have approached the max in a session by typing `:memstats`. If you need to ship a lot of data around,
75-
you can raise this into the megabyte range and expect CS will continue to function. 80K is the default.
76-
77-
For normal operation, when you change `outputsize` you should also change `logsize` to be at least as much, so that
78-
the system can do complete logs. You are welcome to set log size lots smaller if you don't care about the log.
69+
| `outputsize=80000` | is the maximum output that can be shipped by a volley from the bot without getting truncated.
70+
71+
72+
Actually the `outputsize` value is somewhat less, because routines generating partial data
73+
for later incorporation into the output also use the buffer and need some usually small amount of clearance.
74+
You can find out how close you have approached the max in a session by typing `:memstats`.
75+
If you need to ship a lot of data around, you can raise this into the megabyte range and expect CS will continue to function.
76+
80K is the default. For normal operation, when you change `outputsize` you should also change `logsize` to be at least as much,
77+
so that the system can do complete logs. You are welcome to set log size lots smaller if you don't care about the log.
7978

8079

8180
## File options

0 commit comments

Comments
 (0)