Difference between revisions of "SET HISTPATH"

From Recital Documentation Wiki
Jump to: navigation, search
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=SET HISTPATH=
 
 
 
==Class==
 
Error Handling and Debugging
 
 
 
 
==Purpose==
 
==Purpose==
 
Determines whether the current directory name is added to commands stored in the command history file
 
Determines whether the current directory name is added to commands stored in the command history file
Line 15: Line 8:
  
 
==See Also==
 
==See Also==
DISPLAY HISTORY, DO, LIST HISTORY, SET COMPILE, SET DEVELOPMENT, SET DOHISTORY, SET HISTORY
+
[[DB_SAVEHISTORY]], [[DISPLAY HISTORY]], [[DO]], [[LIST HISTORY]], [[SET COMPILE]], [[SET DEVELOPMENT]], [[SET DOHISTORY]], [[SET HISTORY]]
  
  
Line 27: Line 20:
  
 
==Example==
 
==Example==
<pre>
+
<code lang="recital">
 
// Example using config.db file
 
// Example using config.db file
 
set history on
 
set history on
Line 33: Line 26:
 
set history to file myhist
 
set history to file myhist
 
set dohistory on
 
set dohistory on
// End of config.db</pre>
+
// End of config.db</code>
  
  
 
==Products==
 
==Products==
Recital Database Server, Recital Mirage Server, Recital Terminal Developer
+
Recital Server, Recital  
 +
[[Category:Documentation]]
 +
[[Category:Commands]]
 +
[[Category:Set_Commands|HISTPATH]]
 +
[[Category:Error Handling and Debugging]]
 +
[[Category:Error Handling and Debugging Set Commands]]

Latest revision as of 15:54, 23 November 2009

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

DB_SAVEHISTORY, 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 Server, Recital