ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Cc: Marc van Dongen <dongen@cs.ucc.ie>,
	Ed L Cashin <ecashin@coe.uga.edu>,
	Patrick Gundlach <gundlach@irb.cs.uni-dortmund.de>,
	ConTeXt <ntg-context@ntg.nl>
Subject: Re: metapost not invoked? mpgraph.1 not created
Date: 15 Mar 2001 12:10:12 +0100	[thread overview]
Message-ID: <86elvzp9t7.fsf@office.admaster.pl> (raw)
In-Reply-To: <3.0.6.32.20010220174002.00afa980@server-1>

Hans Hagen <pragma@wxs.nl> writes:

> Hi, 
>  
> >Again, I missed Hans' original query, so I don't know if this
> >is relevant.
> 
> It may be relevenat. I hope that the three of you can sort it out, so that
> the solution can go into the faq. 

I don't know whether this is not the same problem I've had. When you
uncompress the context archive it doesn't have the +x bits which make
the scripts being executable.

In texexec 2.5 you have:

sub RunPerlScript
  { my ($ScriptName, $Options) = @_ ;
    if ($dosish)
      { if (-e "$TeXScriptsPath$ScriptName.pl")
          { system ("perl $TeXScriptsPath$ScriptName.pl $Options") } }
    else
      { system ("$ScriptName $Options") } }

Which makes perl try to run the script on UNIX systems without
checking if it's executable (texutil was -x in my case) and, which is
more problematic, doesn't check for possible execution errors. I've
proposed some time ago to change the call to something like:

  ...
  if (! -x $ScriptName) {
        die("Nonexecutable script, fix the permisions for $ScriptName\n");
  } else {
         system ("$ScriptName $Options") or die $!;
  }
  ...

What do you think?

/S


  reply	other threads:[~2001-03-15 11:10 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
2001-02-20 16:40         ` Hans Hagen
2001-03-15 11:10           ` Slawek Zak [this message]
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=86elvzp9t7.fsf@office.admaster.pl \
    --to=zaks@prioris.mini.pw.edu.pl \
    --cc=dongen@cs.ucc.ie \
    --cc=ecashin@coe.uga.edu \
    --cc=gundlach@irb.cs.uni-dortmund.de \
    --cc=ntg-context@ntg.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).