Difference between revisions of "SET HISTPATH"
Yvonnemilne (Talk | contribs) |
Barrymavin (Talk | contribs) (→Example) |
||
| Line 27: | Line 27: | ||
==Example== | ==Example== | ||
| − | < | + | <code lang="recital"> |
// Example using config.db file | // Example using config.db file | ||
set history on | set history on | ||
| Line 33: | Line 33: | ||
set history to file myhist | set history to file myhist | ||
set dohistory on | set dohistory on | ||
| − | // End of config.db</ | + | // End of config.db</code> |
| − | + | ||
==Products== | ==Products== | ||
Revision as of 01:40, 13 March 2009
Contents
SET HISTPATH
Class
Error Handling and Debugging
Purpose
Determines whether the current directory name is added to commands stored in the command history file
Syntax
SET HISTPATH ON | OFF | (<expL>)
See Also
DISPLAY HISTORY, DO, LIST HISTORY, SET COMPILE, SET DEVELOPMENT, SET DOHISTORY, SET HISTORY
Description
The SET HISTPATH command determines whether the current directory name is added to commands stored in the command history file. A command history file is created when SET HISTORY is ON and set to output the history buffer to a file. This is achieved using the SET HISTORY TO FILE command. If SET DOHISTORY is also ON then commands executed from interpreted program files will also be stored in the command history file. Each line that is executed is placed into the file, next to the name, stack number and line number of the executing program, e.g.
/home/recital/test/:keyboard(0:1): do myprog /home/recital/test/:myprog(1:1): do subprog /home/recital/test/:subprog(2:1): open database southwind
Example
// Example using config.db file set history on set histpath on set history to file myhist set dohistory on // End of config.db
Products
Recital Database Server, Recital Mirage Server, Recital Terminal Developer
