Setting up
There are a few preliminaries necessary to
make your life simple. Assuming that PiScript,
a PostScript viewer (such as gv), and Python
are already installed on your computer.
-
If you are running PiScript on your own machine,
download the current package
and the TEX fonts.
Unpack them into what will be your piscript directory.
As bugs are fixed this weekend,
you will want to download and unpack
into the directory piscript the latest file of
patches.
-
On all machines:
tell Python where the basic piscript directory is.
- On Linux or MacOSX, set the
environment variable PYTHONPATH to be that directory.
Exactly how to do this depends on a few details.
On the system here at the BMS, the correct directory is
~cass/. That is to say, the subdirectory
piscript in my own home directory
is openly accessible. I have
done this so I can fix errors rapidly. Please call my attention to them
quickly.
-
On the MacOSX I have worked with or with
shell bash, this is
set in .bashrc or .bash_profile with
export PYTHONPATH=$HOME/python.
With tcsh as shell, it is
set PYTHONPATH=$HOME/python in .tcshrc.
- In Windows: Open Control Panel/System/Advanced/Environment Variables.
Set PYTHONPATH to be the directory containing the functional
PiScript directory.
You can find exactly where this is by searching
for PiScript.py.
-
Set an environment variable LOCALPISCRIPTDIR,
and put this also in your PYTHONPATH.
On my machine this is the `hidden'
directory .piscript in my home directory.
This directory should have in it
a subdirectory configs. The configs directory
should have in it an empty file __init__.py.
The point of this directory
is to be able to store PiScript stuff
that is not overwritten by updates
and also freely accessible to you, such as your own TEX
configuration files.
-
Sooner or later you will
probably want to adjust
your TEX environment in PiScript.
|
|