Here's a setup I've arrived at after several years of use...
alias al alias # Genealogy/LifeLines setenv LLHOME /Volumes/UserDisk/Users/rsimms/g/ll setenv LLDATABASES $LLHOME/data setenv LLEDITOR vi setenv LLPROGRAMS .:$LLHOME/rep setenv LLREPORTS $LLHOME/out al llines $LLHOME/bin/llines al ll 'cd $LLHOME/out;llines main' al lll 'cd $LLHOME/lab;llines' al ll35 $LLHOME/bin/llines3.0.35-r al lll35 'cd $LLHOME/lab;ll35' al ll36 $LLHOME/bin/llines3.0.36-f al lll36 'cd $LLHOME/lab;ll36'
The LLHOME one is just for convenience in creating other shell variables. The LLEDITOR is currently set to the default one, I left it there to remind me how to change over to 'pico' as an experiment.
I have two directories for report programs: 'rep' and 'lab', so if I'm running LL from the 'lab' directory, that LLPROGRAMS path lets me have access to both accepted ones and the under-construction ones. But if I'm not in that directory, then I'll generally only have the ones in 'rep' at my disposal.
The LLREPORTS variable to keep output separate from report programs.
Then there are the aliases...
I keep my LifeLines executables out of the command shell's path. Once I
started accumulating a few different versions I decided to put them under
$LLHOME/bin.
ll is for working on my own data,
llines and lll allow me to specify which database to work on. But the lll one
moves me over to the 'lab' directory first, for developing or testing report
programs.
The others are for specific versions of LL.
Some of these shell variables can also be replaced by user options in LifeLines configuration files.