Workbench User Guide : 13. Writing Scripts and Procedures : How You Can Use Your System Editor
 
Share this page                  
How You Can Use Your System Editor
As an alternative to the Script Editor, you can use your system editor instead. You can specify that Workbench call the system editor by setting the II_W4GL_SYSTEMEDITOR environment variable to TRUE.
II_W4GL_SYSTEMEDITOR
Specifies whether to use a system editor instead of the internal OpenROAD script editor. Possible settings are:
TRUE
Specifies that Workbench should call the system editor specified by II_WINDOWEDIT or II_EDIT environment variables. The system editor is automatically opened instead of the OpenROAD Script Editor.
Note:  For view‑only operations, II_WINDOWVIEW or II_VIEW is used in place of II_WINDOWEDIT or II_EDIT.
The system editor is called automatically for frame and field scripts and procedures.
FALSE
Specifies that Workbench should use its own Script Editor
Default: FALSE
Workbench checks the following environment variables to find the system editor to use:
II_WINDOWEDIT
Specifies the command template to invoke a system editor in edit mode. This is used to specify a system editor that Workbench uses instead of its own Script Editor for editing scripts.
For more information, see How You Can Use Templates for II_WINDOWEDIT and II_WINDOWVIEW.
II_WINDOWVIEW
Specifies the command template to invoke a system editor in read-only or view mode. This is used (for a read-only editor) to specify a system editor that Workbench uses instead of its own Script Editor for viewing scripts.
For more information, see How You Can Use Templates for II_WINDOWEDIT and II_WINDOWVIEW.
II_EDIT
Specifies a system editor that Workbench uses instead of its own Script Editor for editing scripts.
Note:  There is no command template for this variable.
II_VIEW
Specifies a system editor that Workbench uses instead of its own Script Editor for viewing scripts.
Note:  There is no command template for this variable.
Workbench checks the II_WINDOWEDIT and II_EDIT environment variables (in that order) to see if any are set. If one of the variables is set, OpenROAD uses it. Depending on your operating system, Workbench does the following:
Windows
If none of the variables is set, the Windows Notepad is used.
UNIX
If none of the variables is set, the vi editor is used.
Similarly, for a read-only editor, II_WINDOWVIEW, II_VIEW, and ING_EDIT (in that order) are checked.
Windows
If none of the variables is set, the Windows Notepad is used.
UNIX
If none of the variables is set, the vi editor is used.
When you are finished editing a script with the system editor, save or quit from the file as you usually do. Workbench closes the system editor window.