Initialization Files

CUBIT can execute commands on startup, before interactive command input, through initialization files. This is useful if the user frequently uses the same settings.

The following files are played back in order, if they exist, at startup:

$(cubit install directory)/.cubit.install
$HOME/.cubit
$(current working directory)/.cubit

The $(cubit install directory) is determined by the location the program is installed. On Linux and Windows, it'll be the bin directory of the installation and on macOS it'll be the Cubit.app/Contents/MacOS directory.

$HOME is an environment variable pointing to the location of the user's home directory. On Windows, the HOMEDRIVE and HOMEPATH environment variables will be used instead of the HOME environment variable.

The $(current working directory) is determined by where the user starts the program itself.

If the -initfile <filename> option is used on the command that starts cubit, then the other init files are skipped and only the specified filename is played back.

These files are typically used to perform initialization commands that do not change from one execution to the next, such as turning off journal file output, specifying default mouse buttons, setting geometric and mesh entity colors, and setting the size of the graphics window.