I know this seems off topic, but not really...We need to straighten this out
if Linux users are are to be able to use the global .mod file that I already
have working in Windows.
My approach is to require the user to store the path to pmx.mod in an
environment variable PMXMODDIR (Cornelius Noack's suggestion). From within
PMX, I use the FORTRAN statment
call getenv('PMXMODDIR',pathq)
to transfer the name of the path into the character variable pathq, then go
on from there to open pmx.mod and insert the PMX commands it contains into
the virtual pmx file that PMX processes. It all works fine when I run PMX
from a DOS window in Win98. But it doesn't work in RH Linux 9.0. The program
compiles OK with g77 (with the usual 2 changes), and the g77 docs say that
the syntax for getenv() is the same as the Windows version. But on
execution, PMX can't find the environment variable. I both set the
environment variable and run the program from the same bash shell. I think
this has something to do with shell levels and such, and maybe there's a
compiler switch to make it work, but I'm too dumb to figure it out. If
anyone has RH Linux 9.0 and can figure out how to make this work, that would
be great. It might also be useful if someone with another flavor of Linux
could test it out and let me know what's up. The worst case is that only
Windows users will be able to use this feature. I'm not going to drop it, as
I have too much energy invested. Here's a program you could try with g77 to
test the concept:
character*80 pathq
call getenv('PMXMODDIR',pathq)
print*,'PMXMODDIR: ',pathq
end
Before running the test, you can set the environment variable by entering
PMXMODDIR=/whatever/whenever/
on the command line.
--Don Simons
_______________________________________________
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
