The following modifications were made in order to get Gipsy to run
properly under MacOS in a PPC with "bash" as the default shell:

0. Choice of shell:
-------------------
The default shell for MacOS is now "bash". However, the Gipsy documentation
says things work best with the C-shell. We specify this when running Gipsy
by adding the first line in the "runGipsy" command file, to be described
below.

However, before one gets to that point, the Gipsy installation has to be
done, and this also makes use of several command files. A casual perusal of
these various command files leads me to suspect that the
shell is not always specified with a line like "#!/bin/csh" or
"#!/bin/bash". It might be good to check this for consistency just in case
a Mac user forgets to take the necessary precautions.

1. Applescript "gipsy.app" developed.
-------------------------------------
This script starts X11, opens an Xterm with specific choices for some parameters
(window size, font, title, ... ) and executes the command "runGipsy" in it.

Here's the Applescript "gipsy.app":

 tell application "Finder"
  activate
  open application file "X11.app" of folder "Utilities" of folder "Applications" of startup disk
 end tell
 do shell script "sleep 3 && export DISPLAY=:0 && source /sw/bin/init.sh && xterm -geom 80x60+40+50 -T GIPSY -font \"-adobe-courier-bold-r-normal--13-*-*-*-*-*-*-*\" -ls -e ~/runGipsy"
 
 tell application "X11"
  quit
 end tell

This script can be created with any editor as the file "gipsy.app".

The "GIPSY" logo can be attached as an icon to this script in a Mac
as follows:

  1. Open the gipsy logo "gif" file with Preview, and select the part you want.
  2. Copy the selected area using, for instance, the Edit menu, or "CMD+C".
  3. Single click on the apple script file "gipsy.app" in the Finder.
  4. Get the "info" pane for the file; the simplest way is to use "CMD+I".
  5. Single click on the little icon at the top left corner of this pane.
  6. Paste the copied area over it with "CMD+V".
  7. Close the pane with "CMD+W", and you're done.

2. ".cshrc" file defined.
------------------------
This is needed because we want to run Gipsy under the C shell, and we
need to control the order of directories in the PATH environment variable.

Here it is:

 #
 # .chsrc file, for use primarily with e.g. GIPSY
 #
 source $HOME/.scienv
 setenv PATH ${PATH}:${HOME}/bin:/sw/bin
 #
 echo "This is the C-shell"
 #
 # end of .cshrc
 #


3. "runGipsy" C-shell script developed.
--------------------------------------
The main purpose of this executable file is to set some environment variables
and define working directories. The default runs gipsy in "~/GipsyWorkspace",
but this can be changed on starting the executable.

Here is "runGipsy":
 
 #!/bin/csh -f
 
 #  This is a C-shell script to run GIPSY on a Mac, developed at STScI by
 #  Giuseppe Romeo and Ron Allen under OSX 10.4.11 in April-May 2008.
 #
 #   Assuming this script is called "runGipsy", it can be started at the
 #   Xterminal prompt with:
 #
 #      runGipsy (will default to run in ~/GipsyWorkspace"), or
 #
 #      runGipsy -d directory_name (will pushd this directory on the stack
 #         and then run Gipsy)
 #
 # this command file defines Gipsy's directories:
 
 setenv WEB_BROWSER Netscape
 source ~/.packages/.gipsy.csh
 #
 set dir=''
 while ( $#argv >= 1 )
 
  switch ( $1 )
 
  case "-d" :
  if ( $#argv > 1 ) then
   set dir = $2
   shift
    else
   echo "need a directory name"
   exit
    endif
    breaksw
 
  endsw
 
    shift
 
 end
 
 # In case the directory is not defined, then default to this value:
 
 if ( $dir == '') then
    set dir = "~/GipsyWorkspace"
 endif
 
 pushd $dir
 
 gipsy
 
 reset
 clear
 
 # return to the initial directory when Gipsy terminates
 popd
 
 exit 0
 
 # end of C-shell script.

4. Tweaks made to "HERMES.def"
-----------------------------
I dislike terminal bells, so here is the place to define:

 beep=off

Also we need to fool Hermes into using "Firefox" instead of "Netscape" (which is
no longer supported at STScI) so we can start the browser from the Gipsy xterm
window with ESC+X. This also gives us the opportunity to start Firefox using the
standard MacOSX "open" command, which has additional advantages. The kluge
begins with defining the environment variable in Hermes.def:

 web_browser=/Users/rjallen/bin/Netscape

... and creating an executable called "Netscape" in ~/bin in your home directory
(you may have to create this subdirectory if it's not already there).

5. bash script "Netscape" defined:
----------------------------------
This is the other part of the "Firefox" kluge. A bash script called "Netscape"
was developed for this and inserted e.g. into /Users/rjallen/bin/ (we use bash
here at STScI because that's the default for MacOSX).

The script picks up the gipsy URL from Hermes, and opens Firefox with it using
the MacOSX "open" command. This has the advantage that if Firefox is already
active, you can set up Firefox to open the gipsy web page in a new "tab".

Here's the "Netscape" bash script:

 #!/bin/bash
 
 # pick up the url listed after the "Netscape" command:
 #
 url=$1
 #
 #echo "URL=$url\n"
 #
 # open Firefox the Mac way:
 #
 `open -a Firefox $url`
 #

Note that the choice of the "~/bin" directory for this script is arbitrary.
You can put it wherever you like, just be sure that the web_browser definition
in "Hermes.def" refers to it.

6. Automatic updates enabled:
-----------------------------
a). These have been set up to run weekly. The "crontab" file entry for this can
be constructed as follows. First, obtain the current contents of your own cron
table and write them in a text file (e.g. crontab.txt) with:

 crontab -l > ~/crontab.txt
 
Next, edit this text file with the editor of your choice, adding the following
lines:

 # crontable entry for weekly updates of GIPSY on Tuesday at 10 pm
 0 22 * * 2 /bin/csh /usr/local/gipsy/sys/update.csh
 # structure of this line:
 # minute ; hour ; day of month ; day of the year ; day of the week

Now load the new cron table with the command:

 crontab crontab.txt

In the example above the updates run every Tuesday evening at 10 pm.

b). The g77 compiler must be in place for these updates to be processed
correctly. This means that, for instance, the location where g77 is must be
included in the $PATH variable.