From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4189 Path: main.gmane.org!not-for-mail From: Ed L Cashin Newsgroups: gmane.comp.tex.context Subject: Re: metapost not invoked? mpgraph.1 not created Date: 21 Feb 2001 11:53:18 -0500 Sender: owner-ntg-context@let.uu.nl Message-ID: References: <3.0.6.32.20010220125344.01cc87b0@server-1> <20010220155806.B15049@cs.ucc.ie> <20010221125141.B16050@cs.ucc.ie> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035394877 23675 80.91.224.250 (23 Oct 2002 17:41:17 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:41:17 +0000 (UTC) Cc: Hans Hagen , Patrick Gundlach , ConTeXt Original-To: Marc van Dongen In-Reply-To: Marc van Dongen's message of "Wed, 21 Feb 2001 12:51:41 +0000" Xref: main.gmane.org gmane.comp.tex.context:4189 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4189 Marc van Dongen writes: > Ed L Cashin (ecashin@coe.uga.edu) wrote: > > : > it may well be that because it is not exported its value may be > : > /usr/local/bin > : > : Usually some system-wide resource configuration ("rc") file has > : already exported the $PATH shell variable. (It doesn't hurt to export > : it again, though.) > > The point is, if people add things to the path *after* it is > exported or add thing to the path as part of a shell-script, > these additions will not be made known to subshells. You > *have* to export it again. That's not true for Bourne-style shells: $ foo=hi $ perl -e 'print $ENV{"foo"} . "\n"' $ export foo $ perl -e 'print $ENV{"foo"} . "\n"' hi $ foo=hi,there $ perl -e 'print $ENV{"foo"} . "\n"' hi,there I wouldn't know about C shells. -- --Ed Cashin integrit file verification system ecashin@coe.uga.edu http://integrit.sourceforge.net/