A

---

Hierarchy Editor Environment Variables

---

This section provides information on the names, descriptions, and graphical user interface equivalents for the hierarchy editor environment variables.

The local hed.env file is typically created with the File – Save Defaults command and must be in a directory that is listed in your setup.loc file (for example, your home directory or current working directory). The local hed.env file contains only those settings that are different from the registration hed.env file.

The hed.env file is read by the Hierarchy Editor when it is started. If you have multiple hed.env files, the Hierarchy Editor determines which value to use for each variable based on the search order defined in the setup.loc file. For more information about the setup.loc file, see, Cadence Setup Search File: setup.loc.

Some of the form and display settings, typically the general user interface settings, are saved when you use the File – Save Defaults command. For example, the options that you select in the Options form or in the Filters form are saved when you use the File – Save Defaults command. Other settings, such as the list of views in the Edit Constants form, can only be changed by editing the hed.env file manually.

You can use a semicolon to comment out a line in your hed.env file. The comment character must be the first character in the line. For example:

; My defaults

hed.constants viewChoices string "schematic symbol verilog verilogAMS"