Update ChatScript-Advanced-User-Manual.md

solyarisoftware · web-flow · commit a90de7124b25 · 2017-02-07T11:20:19.000+01:00
diff --git a/WIKI/ChatScript-Advanced-User-Manual.md b/WIKI/ChatScript-Advanced-User-Manual.md
@@ -1,8 +1,7 @@
-﻿# ChatScript Advanced User's Manual
-
-> © Bruce Wilcox, gowilcox@gmail.com brilligunderstanding.com 
-
-> Revision 1/28/2017 cs7.12
+# ChatScript Advanced User's Manual
+© Bruce Wilcox, gowilcox@gmail.com www.brilligunderstanding.com 
+<br>Revision 1/28/2017 cs7.12
+<br><br>
 
 * [Review](ChatScript-Advanced-User-Manual.md#review-overview-of-how-cs-works)
 * [Advanced Concepts](ChatScript-Advanced-User-Manual.md#advanced-concepts)
@@ -102,14 +101,15 @@ CS just directly embeds the arguments in the string and any attempt to use
 the active string implicitly invokes the equivalent of sprintf.
 
 User variables also come in permanent and transient forms. 
-<br>**Permanent variables** start with a single `$` and are preserved across user interactions 
-(are saved and restored from disk). You can see and alter their value from anywhere.
 
-<br>**Transient variables** start with `$$` and completely disappear when a user interaction
-happens (are not saved to disk). You can see and alter their value from anywhere.
+- **Permanent variables**
+  start with a single `$` and are preserved across user interactions  (are saved and restored from disk). You can see and alter their value from anywhere.
 
-<br>**Local variables** (described later) start with `$_` and completely disappear when a user interaction
-happens (are not saved to disk). You can see and alter their value only within the topic or outputmacro they are used.
+- **Transient variables**
+  start with `$$` and completely disappear when a user interaction happens (are not saved to disk). You can see and alter their value from anywhere.
+
+- **Local variables** 
+  (described later) start with `$_` and completely disappear when a user interaction happens (are not saved to disk). You can see and alter their value only within the topic or outputmacro they are used.
 
 
 ### Facts 
@@ -234,17 +234,16 @@ was this
 ```
     ^myfunction( $myvar 1)
 ```
-then the effect of `^argument1 += 1` is as though `$myvar += 1` were done and `$myvar` would now be one
-higher. Of course, had you tried to do
-`^argument2 += 1` then that would be the illegal `1 += 1` and the assignment would fail.
+then the effect of `^argument1 += 1` is as though `$myvar += 1` were done and `$myvar` would now be one higher. 
 
+Of course, had you tried to do `^argument2 += 1` then that would be the illegal `1 += 1` and the assignment would fail.
 
 ```
 outputmacro: ^myfunction( $_argument1 $_argument2)
     $_argument1 += 1
 ```
 
-Use of $_ variables in the function definition is a call by value. All $_ variables are purely local and cannot
+Use of `$_` variables in the function definition is a call by value. All `$_` variables are purely local and cannot
 be seen outside of the function (or topic) they are used in. You can also mix call by reference and call by
 value arguments.
 
@@ -299,7 +298,8 @@ Concepts can be built from other concepts that do not have specific words.
 Concept: ~myconcept (!thisword ~otherconcept)
 ```
 
-Note: the system has two kinds of concepts. Enumerated concepts are ones formed from an explicit list of members. Stuff in definitions of concept: ~xxx()  are that. There are also internal concepts marked by the system. These include part of speech of a word (requires using the pos-tagger to decide from the input what part of speech it was of possibly several), grammatical roles, words from infinite sets like ~number and ~placenumber and ~weburl, and so forth.  
+Note: the system has two kinds of concepts. Enumerated concepts are ones formed from an explicit list of members. Stuff in definitions of `concept: ~xxx()` are that. 
+There are also internal concepts marked by the system. These include part of speech of a word (requires using the pos-tagger to decide from the input what part of speech it was of possibly several), grammatical roles, words from infinite sets like `~number` and `~placenumber` and `~weburl`, and so forth.  
 
 In a pattern of some kind, if you are referencing a sentence location using a match variable, you can match both kinds of concepts. But if you are not tied to a location in  a sentence, you can't match internally computed ones. So something like
 ```
@@ -323,13 +323,13 @@ When a topic is executing rules, it does not stop just because a rule matches. I
 executing rules until some rule generates ouput for the user or something issues an
 appropriate `^end` or `^fail` call. So you can do things like this:
 ```
-u: (I love) $userloves = true
+u: ( I love ) $userloves = true
 
 u: ( dog ) $animal = dog
 
-u: ( love) Glad to hear it
+u: ( love ) Glad to hear it
 
-u: ( dog) I hate dogs
+u: ( dog ) I hate dogs
 ```
 and given _I love dogs_, the system will set $userloves and $animal and output glad to
 hear it.
@@ -344,27 +344,27 @@ topic: ~rust keep random [rust iron oxide]
 ```
 The flags and their meanings are:
 
-|flag         |  description                        |
-|-------------|-------------------------------------|  
-|`Random`     |    search rules randomly instead of linearly
-|`NoRandom`   |    (default) search rules linearly
-|`Keep`       |    do not erase responders ever. Gambits (and rejoinders) are not affected by this
-|`Erase`      |    (default) erase responders that successfully generate output.<br>Gambits automatically erase unless you suppress them specifically.
-|`NoStay`     |    do not consider this a topic to remain in, leave it (except for rejoinders)
-|`Stay`       |   (default) make this a pending topic when it generates output
-|`Repeat`     |    allow rules to generate output which has been output recently
-|`NoRepeat`   |    (default) do not generate output if it matches output made recently
-|`Priority`   |    raise the priority of this topic when matching keywords
-|`Normal`     |    (default) give this topic normal priority when matching keywords
-|`Deprioritize`|   lower the priority of this topic when matching keywords
-|`System`      |   this is a system topic. It is automatically `NoStay`, `Keep`.<br>`Keep` automatically applies to gambits as well. The system never looks to these topics for gambits. System topics can never be considered pending (defined shortly). They can not have themselves or their rules be enabled or disabled. Their status/data is never saved to user files.
-|`User`        |   (default) this is a normal topic
-|`NoBlocking`  |   should not perform any blocking tests on this topic in `:verify`
-|`NoPatterns`  |   should not perform any pattern tests on this topic in `:verify`
-|`NoSamples`   |   should not perform any sample tests on this topic in `:verify`
-|`NoKeys`      |   should not perform any keyword tests on this topic in `:verify`
-|`More`        |   normally if you try to redeclare a concept, you get an error. `MORE` tells CS you intend to extend the concept and allows additional keywords.
-|`Bot=name`    |   if this is given, only named bots are allowed to use this topic. See `ChatScript Multiple Bots manual`
+|flag              |  description 
+|:----------------:|-------------- 
+|__`Random`__      |    search rules randomly instead of linearly
+|__`NoRandom`__    |    (default) search rules linearly
+|__`Keep`__        |    do not erase responders ever. Gambits (and rejoinders) are not affected by this
+|__`Erase`__       |    (default) erase responders that successfully generate output.<br>Gambits automatically erase unless you suppress them specifically.
+|__`NoStay`__      |    do not consider this a topic to remain in, leave it (except for rejoinders)
+|__`Stay`__        |   (default) make this a pending topic when it generates output
+|__`Repeat`__      |    allow rules to generate output which has been output recently
+|__`NoRepeat`__    |    (default) do not generate output if it matches output made recently
+|__`Priority`__    |    raise the priority of this topic when matching keywords
+|__`Normal`__      |    (default) give this topic normal priority when matching keywords
+|__`Deprioritize`__|   lower the priority of this topic when matching keywords
+|__`System`__      |   this is a system topic. It is automatically `NoStay`, `Keep`.<br>`Keep` automatically applies to gambits as well. The system never looks to these topics for gambits. System topics can never be considered pending (defined shortly). They can not have themselves or their rules be enabled or disabled. Their status/data is never saved to user files.
+|__`User`__        |   (default) this is a normal topic
+|__`NoBlocking`__  |   should not perform any blocking tests on this topic in `:verify`
+|__`NoPatterns`__  |   should not perform any pattern tests on this topic in `:verify`
+|__`NoSamples`__   |   should not perform any sample tests on this topic in `:verify`
+|__`NoKeys`__      |   should not perform any keyword tests on this topic in `:verify`
+|__`More`__        |   normally if you try to redeclare a concept, you get an error. `MORE` tells CS you intend to extend the concept and allows additional keywords.
+|__`Bot=name`__    |   if this is given, only named bots are allowed to use this topic. See `ChatScript Multiple Bots manual`
 
 
 ## Rules that erase and repeat
@@ -934,7 +934,7 @@ the `_` equivalent) is a single item, whereas ( take charge) is 4 items.
 
 So the first rule will below will match faster than the second rule:
 ```
-u: ( "I love you today when")
+u: ("I love you today when")
 
 u: (I love you today when)
 ```
@@ -1796,22 +1796,14 @@ and have the system automatically generate gestures during postprocessing on its
 The stand-alone engine and the WEBINTERFACE/BETTER scripts automatically handle
 the following oob outputs:
 
-**Callback**: The webpage or stand-alone engine will wait for the designated milliseconds
-and if the user has not begun typing will send in the oob message [callback] to CS. If user
-begins typing before the timeout, the callback is cancelled.
-e.g. `[callback=3000]` will wait 3 seconds.
+- **Callback**
+  The webpage or stand-alone engine will wait for the designated milliseconds and if the user has not begun typing will send in the oob message [callback] to CS. If user begins typing before the timeout, the callback is cancelled. e.g. `[callback=3000]` will wait 3 seconds.
 
-**Loopback**: The webpage or stand-alone engine will wait for the designated milliseconds
-after every output from CS and if the user has not begun typing will send in the oob
-message [loopback] to CS. If user begins typing before the timeout, the loopback is
-cancelled for this output only, and will resume counting on the next output.
-e.g. `[loopback=3000]` will wait 3 seconds after every output.
+- **Loopback** 
+  The webpage or stand-alone engine will wait for the designated milliseconds after every output from CS and if the user has not begun typing will send in the oob message [loopback] to CS. If user begins typing before the timeout, the loopback is cancelled for this output only, and will resume counting on the next output. e.g. `[loopback=3000]` will wait 3 seconds after every output.
 
-**Alarm**: The webpage or stand-alone engine will wait for the designated milliseconds and
-then send in the oob message [alarm] to CS. Input typing has no effect.
-e.g. `[alarm=3000]` will wait 3 seconds and then send in the alarm.
-CS can cancel any of these by sending an oob message with a milliseconds of 0.
-e.g. `[loopback=0 callback=0 alarm=0]` cancels any pending callbacks into the future.
+- **Alarm**
+  The webpage or stand-alone engine will wait for the designated milliseconds and then send in the oob message [alarm] to CS. Input typing has no effect. e.g. `[alarm=3000]` will wait 3 seconds and then send in the alarm. CS can cancel any of these by sending an oob message with a milliseconds of 0. e.g. `[loopback=0 callback=0 alarm=0]` cancels any pending callbacks into the future.
 
 
 # System callback functions 
@@ -2091,7 +2083,7 @@ Normally lower case words would break up a title.
 
 # Common Script Idioms
 
-## Selecting Specific Cases ^refine
+## Selecting Specific Cases `^refine`
 
 To be efficient in rule processing, I often catch a lot of things in a rule and then refine it.
 ```
@@ -2144,6 +2136,7 @@ u: (where * you * live) ^reuse(HOUSE)
 The rule on disabling a rule after use is that the rule that actually generates the output gets disabled. 
 So the default behavior (if you don't set keep on the topic or the rule) is that if the question is asked first, 
 it reuses HOUSE. 
+
 Since we have given the answer, we don't want to repetitiously volunteer it, HOUSE gets disabled. 
 But, if the user repetitiously asks the question (maybe he forgot the answer), we will answer it again because the responder
 didn't get disabled, just the gambit. And disabling applies to allowing a rule to try to
