Closed Issue: SET DOHISTORY command description is missing in VFP 9 SP2 help [30560]

SET DOHISTORY has a new meaning in VFP 9, so it should not be described only as a "Backward compatible" command.
 
My suggestion:
 
Title:
Determines whether or not commands from a program are placed into the Debug Output window.
 
Syntax:
SET DOHISTORY ON | OFF
 
Parameters:
ON
places commands from a program into the Debug Output window as the program executes.
 
OFF
(default) doesn't place commands from a program into the Debug Output window.
 
Remarks:
Use SET DOHISTORY only as a debugging aid to isolate particularly stubborn bugs. SET DOHISTORY ON has no effect when the program is running under the run-time library environment or when the Debug Output window does not exist in IDE. Commands directly executed from Command window aren't placed into the Debug Output window. Scripts executed via EXECSCRIPT() function behave like a standard program code and they are placed into the Debug Output window.
 
See also:
DEBUG
DEBUGOUT
SET ECHO
SET STEP
EXECSCRIPT()
 
 
 
Additional updates forced by this topic in the help file:
 
1) SET Command Overview - please update the SET DOHISTORY description
2) SET() function - please add "DOHISTORY" and "ON or OFF" into the table describing allowed parameters of this function
3) SET ECHO - please add SET DOHISTORY into the See also part
4) SET STEP - please add SET DOHISTORY into the See also part
5) DEBUG - please add SET DOHISTORY into the See also part
6) DEBUGOUT - please add SET DOHISTORY into the See also part
7) Please move the SET DOHISTORY command into the appropriate place in TOC (remove it from "Backward comaptible commands" and create an entry in "Commands" section)