Load search path?

Google Group
1

Hi all,

What determines the search path for staload and dynload when calling patsopt?

Thanks,
Shea

2

the search path ranges over the following in the listed order:

the current directory of the filename being processed

the ones in PATHLST (added by the flag -IATS)

the ones in PREPATHLST (${PATSHOME} is the only one as of now)

Is PATHLST an internal variable? I tried to define and export it as
environment variable, with no effect. Seems only the -IATS command line
option has an effect. Still about this option, I noticed it does not appear
in the help displayed by patsopt --help.

3

Ah ha, thanks! I just tried -I :)> On Mar 6, 2015, at 2:36 PM, gmhwxi gmh...@gmail.com wrote:

the search path ranges over the following in the listed order:

the current directory of the filename being processed

the ones in PATHLST (added by the flag -IATS)

the ones in PREPATHLST (${PATSHOME} is the only one as of now)

On Friday, March 6, 2015 at 2:16:59 PM UTC-5, Shea Levy wrote:
Hi all,

What determines the search path for staload and dynload when calling patsopt?

Thanks,
Shea

–
You received this message because you are subscribed to the Google Groups “ats-lang-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ats-lang-user...@googlegroups.com mailto:ats-lang-user...@googlegroups.com.
To post to this group, send email to ats-lan...@googlegroups.com mailto:ats-lan...@googlegroups.com.
Visit this group at http://groups.google.com/group/ats-lang-users http://groups.google.com/group/ats-lang-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ats-lang-users/9ff306b0-83ad-4609-a596-558f8b247b5b%40googlegroups.com https://groups.google.com/d/msgid/ats-lang-users/9ff306b0-83ad-4609-a596-558f8b247b5b%40googlegroups.com?utm_medium=email&utm_source=footer.

4

the search path ranges over the following in the listed order:

the current directory of the filename being processed

the ones in PATHLST (added by the flag -IATS)

the ones in PREPATHLST (${PATSHOME} is the only one as of now)On Friday, March 6, 2015 at 2:16:59 PM UTC-5, Shea Levy wrote:

Hi all,

What determines the search path for staload and dynload when calling
patsopt?

Thanks,
Shea

5

As of now, PATHLST cannot be set using an environment variiable.

We could introduce ATSPATH and ATSPREPATH in the future. Let’s wait a bit.On Mon, May 11, 2015 at 2:32 PM, ‘Yannick Duchêne’ via ats-lang-users < ats-lan...@googlegroups.com> wrote:

Le vendredi 6 mars 2015 20:36:45 UTC+1, gmhwxi a écrit :

the search path ranges over the following in the listed order:

the current directory of the filename being processed

the ones in PATHLST (added by the flag -IATS)

the ones in PREPATHLST (${PATSHOME} is the only one as of now)

Is PATHLST an internal variable? I tried to define and export it as
environment variable, with no effect. Seems only the -IATS command line
option has an effect. Still about this option, I noticed it does not appear
in the help displayed by patsopt --help.

–
You received this message because you are subscribed to the Google Groups
“ats-lang-users” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ats-lang-user...@googlegroups.com.
To post to this group, send email to ats-lan...@googlegroups.com.
Visit this group at http://groups.google.com/group/ats-lang-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ats-lang-users/44e62a8e-56cb-418c-8c12-7a573f6495ce%40googlegroups.com
https://groups.google.com/d/msgid/ats-lang-users/44e62a8e-56cb-418c-8c12-7a573f6495ce%40googlegroups.com?utm_medium=email&utm_source=footer
.