From: Marc van Dongen <dongen@cs.ucc.ie>
Cc: Hans Hagen <pragma@wxs.nl>,
Patrick Gundlach <gundlach@irb.cs.uni-dortmund.de>,
ConTeXt <ntg-context@ntg.nl>
Subject: Re: metapost not invoked? mpgraph.1 not created
Date: Tue, 20 Feb 2001 15:58:06 +0000 [thread overview]
Message-ID: <20010220155806.B15049@cs.ucc.ie> (raw)
In-Reply-To: <m37l2l4az8.fsf@coe.uga.edu>; from ecashin@coe.uga.edu on Tue, Feb 20, 2001 at 10:42:35AM -0500
Ed L Cashin (ecashin@coe.uga.edu) wrote:
: Hans Hagen <pragma@wxs.nl> writes:
:
: > Are there unix people out there (i know there are) ?
Sorry Hans, I didn't spot your original query.
: The UN*X PATH variable works similarily to the DOS PATH variable, so
Not quite. In DOS it is by default made known to subprocesses.
In UNIX you have to explicitly say it should by uttering some
magic spell like:
PATH=/abra/ka/dabra:/abra/kebab/ra
eport PATH
or
export PATH=/abra/ka/dabra:/abra/kebab/ra
if you're using bash or sh
or
setenv PATH /abra/ka/dabra:/abra/kebab/ra
if you're using (tc)sh
: although I am a unix person out here, I don't have any special
: insight. (Of course, it's not necessary for mptopdf or the format
: file to be literally in the PATH.)
Even if
echo $PATH
sez
/abra/ka/dabra:/abra/kebab/ra
it may well be that because it is not exported its value may be
/usr/local/bin
Again, I missed Hans' original query, so I don't know if this
is relevant.
Regards,
Marc
--
Marc van Dongen, CS Dept | phone: +353 21 4903578
University College Cork, NUIC | Fax: +353 21 4903113
College Road, Cork, Ireland | Email: dongen@cs.ucc.ie
next prev parent reply other threads:[~2001-02-20 15:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Mon, 19 Feb 2001 17:22:59 +0100." <3.0.6.32.20010219172259.0157a600@server-1>
2001-02-20 10:48 ` Patrick Gundlach
2001-02-20 11:53 ` Hans Hagen
2001-02-20 15:42 ` Ed L Cashin
2001-02-20 15:58 ` Marc van Dongen [this message]
2001-02-20 16:40 ` Hans Hagen
2001-03-15 11:10 ` Slawek Zak
2001-03-15 11:14 ` Slawek Zak
2001-03-15 12:41 ` Patrick Gundlach
2001-03-15 19:45 ` Ed L Cashin
2001-02-20 21:22 ` Ed L Cashin
2001-02-21 12:51 ` Marc van Dongen
2001-02-21 16:53 ` Ed L Cashin
2001-02-21 17:17 ` Marc van Dongen
2001-02-21 17:22 ` Marc van Dongen
2001-02-21 2:08 ` Uwe Koloska
2001-02-22 15:55 Patrick Gundlach
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 15:39 Patrick Gundlach
[not found] <Your message of "Tue, 20 Feb 2001 12:53:44 +0100." <3.0.6.32.20010220125344.01cc87b0@server-1>
2001-02-20 14:16 ` Patrick Gundlach
2001-02-20 16:46 ` Hans Hagen
2001-02-20 21:35 ` Ed L Cashin
2001-02-20 14:13 Patrick Gundlach
[not found] <Your message of "Mon, 19 Feb 2001 15:59:52 +0100." <3.0.6.32.20010219155952.019f7180@server-1>
2001-02-19 15:47 ` Patrick Gundlach
2001-02-19 16:22 ` Hans Hagen
[not found] <Your message of "Mon, 19 Feb 2001 11:47:49 +0100." <3.0.6.32.20010219114749.017fb4d0@server-1>
2001-02-19 12:57 ` Patrick Gundlach
2001-02-19 14:59 ` Hans Hagen
2001-02-21 2:16 ` Uwe Koloska
2001-02-17 15:24 Patrick Gundlach
2001-02-19 10:47 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010220155806.B15049@cs.ucc.ie \
--to=dongen@cs.ucc.ie \
--cc=gundlach@irb.cs.uni-dortmund.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).