Some changes for the the next release...

George,

Documentation (v3.1.24350) hiccups I found on my travels
--------------------------------------------------------

Article: Keyboard Macros
Heading: Contents of Article
Issue: INOP Link: Saving/Editing key content as .DO Files
Issue: INOP Link: Case Study: Making editing easier on laptops

Heading: Introduction
Issue: Refer to Command Macro Support for more information - INOP Link: Command Macro Support

Heading: Case Study: Implementing Bookmarks
Question: Is this section, and its link in the Contents of Article above, still required, given that we have (TRACK) to perform this function?
===> This case study was an example of how to use key mapping. It's not really doing the same thing as TRACK does. I recommend keeping this. R
------------------------------------------------------------

Article: Automatic Colorization Files
Heading: Contents
Issue: INOP Link: Sample Colorize File
------------------------------------------------------------

Article: Find a character string
Heading: Operands
Section: color-selection-criteria
Issue: INOP Link: Color Selection Criteria Specification
------------------------------------------------------------

Article: List Of Keyboard Primitives
Heading: (CMarkDown) (CMarkLeft) (CMarkRight) (CMarkUp)
Issue: Typo "waill" instead of "will" in each case of sentence:
"...If nothing is marked, it waill act like a normal..."
------------------------------------------------------------

Article: List Of Keyboard Primitives
Heading: (PA2)
Issue: Following statement is no longer true - PA2 no longer 'toggles'
"As long as you press no other keys, you can repeatedly toggle PA2 to go back and forth between the original and the modified version
of the screen. If you do this back-and-forth toggle, the reset line commands will not be restored"

Article: SET a command Variable
Heading: Syntax
Issue: Unlike other primary commands, the operands for the command "SET <variable-name> OFF" are positional.
i.e. they must appear in THAT order. 

The command "SET OFF <variable-name>" is rejected with message "Malformed SET operands"

We should add a warning to the Syntax part for the OFF operand that operands are positional.

(It matters because a macro might specify SPF_CMD("SET OFF "+string_var$) which will not work, in preference to the correct but more clumsy SPF_CMD("SET "+string_var$+" OFF").)

===> Stefan, SPF_CMD can take multiple arguments, and if you do that, it will concatenate them with a blank in between them. That means, SPF_CMD("SET "+string_var$+" OFF") can be rewritten as,

SPF_CMD("SET", string_var$, "OFF")

Does that look less "clumsy"?

<=== R