vem are specified in the file $PTOLEMY/lib/pigiXRes9, and also pigiXRes9.bw and pigiXRes9.cp. These files define a set of X window resources. The pigiXRes9.bw file is used if pigi is started with the -bw option. The .pigiXRes9.cp file is used in pigi is started with the -cp option. The definitions in these files can be overridden by the user. For example, a user who prefers to use microscopic fonts could set the X resource as follows:
$PTOLEMY/lib/pigiXRes9*.The fonts for tk (and hence, the fonts for most of the dialog boxes) are specified in
$PTOLEMY/lib/tcl/ptkOptions.tcl. These may similarly require modifications at some sites. In the worst case, if many standard fonts are not available, it may be necessary to redefine the default fonts built into the tk source code, and recompile tk. You may find the X11 program xlsfonts useful.
xedit is a program provided with Ptolemy to display text files on your screen during a Ptolemy run. Over time, we plan on using tycho, the Ptolemy syntax editor, as a replacement for xedit.If there is some problem with
xedit that you cannot solve, or you do not like xedit, it is possible to change the display program used by Ptolemy. To do this, you need to set the PT_DISPLAY environment variable before you run pigi. For example, to use PT_DISPLAY to view files in a separate tycho window, do:
setenv PT_DISPLAY "tycho %s"To use
PT_DISPLAY to view files in a new xterm window with the vi editor, do
setenv PT_DISPLAY "xterm -e vi %s"The value of the
PT_DISPLAY variable is a printf format string with one %s in it. That %s is replaced with the file to be viewed, for look-inside commands and to view generated code. The default value is "xedit %s".
(setq auto-mode-alist (cons '("\\.pl$" . c++-mode) auto-mode-alist))
pigi) to have access to a very restricted set of colors. If when you start pigi, the welcome window appears in black and white, then you may have such a situation. If the situation is worse, and there are not enough colors in the colormap for vem to start, then you may not even get this far. One solution is simply to exit the offending application (e.g., FrameMaker or Netscape), and restart pigi. A better solution is to configure the offending application to use fewer slots in the colormap. We have found that for FrameMaker 5, the following X resources (placed in your .Xdefaults file) usually solve the problem:
The HP window system, VUE, may not display the correct colors when running Ptolemy. If the Vem window appears with white text on a tan background, or if the Ptolemy run window appears blue instead of tan, then VUE is getting the Ptolemy colors wrong.
The solution here is force VUE to use the regular Ptolemy X resources. Before starting
pigi, in an xterm, do the following line:xrdb -load $PTOLEMY/.Xresources
Then run pigi.
twm sometimes crashes when you are running Ptolemy. We do not know why. It seems to be an interaction with Tk. Our solution is to simply restart it. You may wish to make sure your configuration does not log you out when the window manager exits.