These variables control behavior of the WRspice shell. Most of these variables can be set indirectly from the Shell Options tool from the Shell button in the Tools menu of the Tool Control window.
With this variable unset, the legacy behavior is maintained, i.e., variables set in .options will work in variable substitution, but will be ignored in most commands.
In releases prior to 2.2.61, when a variable is set in a .options line, it becomes visible almost like it was set with the set command, when the circuit containing the .options line is the current circuit. In the variables listing (set command without arguments or the Variables tool), these have a `+' in the first column. However, they are not part of the normal variable database, and they only ``work'' in special cases. For example, they will work in variable substitution, but won't affect the defaults in most commands, such as the plot command. If the same variable is also set with set, the set definition will have precedence. The variables set with .options can't be unset, except by changing the current circuit.
This was confusing to the user. If a .options line contains an assignment for a plot-specific variable (for example), the variable will appear to be active when listed, but it will have no effect on the plot command.
It can be argued that making the circuit variables behave the same as those set with the set command would be an improvement. In this case, variables listed in the set or Variables tool listing will always have effect, and one can set any variable in the .options line, and have it always ``work''.
On the other hand, circuit variables can't be unset, so a variable in the current circuit would always have effect, desired or not. Also, changing present behavior would possibly adversely affect existing users who expect the current behavior, and this change might break existing scripts.
The cktvars variable gives the user control over how to handle the circuit variables.
This variable is ignored under Microsoft Windows. The editing is always enabled in that case.
If nomoremode is set, all output will be printed without pauses.
q Discard the rest of the output c Print the rest of the output without pausing ? Print a help message
0 default ``auto'' mode. 1 off, don't attempt to revert focus. 2 assume older linux, e.g. CentOS 6 and Gnome. 3 assume newish linux, e.g., CentOS 7 and KDE. 4 Apple Mac. 5 Microsoft Windows.
( /path/to/dir1 /path/to/dir2 "/usr/bill/my files" )If a directory path contains white space, it should be quoted, as above.
Unfortunately, not all window managers are cooperative, or know the protocols. By setting this variable, a slightly more brute-force approach is taken to keep the terminal window from losing focus. This may fix the problem, but in some cases this may have side-effects, such as causing pop-up windows to appear below existing windows. Anyway, if the terminal window loses focus when another window pops up, and the user finds this annoying, then setting this boolean variable in the .wrspiceinit file might fix the problem.