iraf.net

Joe, This mail got bounced a while back, so I will sent it again. Another
comment about not having a .cshrc - not only is it possible to do a
source .login, you can put this in a .rootmenu in your unix login directory
so that it happens automatically when you open a new window, e.g., Gterm gterm -Wh 40 -I "source ~/.login"I don't recall hearing if the subprocess spawning problem was ever solved.
Let us know if this is still a problem.--------------old mail---------------
You don't need to log out and back in, just do a 'source .login' when the
window comes up. We will probably switch to a .cshrc at some point, but
for speed and other reasons we haven't done so yet.I understand the problem with the #include <iraf.h> in iraf C source files,
but the construct is portable, and after all we did manage to get the systems
tie-in down to only the one file (it is easy to use a private directory
for the commands and setenv path accordingly, as you suggested). I am leery
of the -I command line option since this is a nonstandard feature of C
compilers, and the iraf source must be compiled on many machines, including
VMS and AOS/VS machines, as well as UNIX machines, without any modifications
to the source files.Your cannot spawn subprocess problem is very strange, no one has ever
reported such a problem before. Maybe it is a bug in ultrix/iraf - site
support will be looking into it. Regards,
Doug Tody