From:	Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: shell scripts in DJGPP
Date:	8 Feb 2000 16:05:23 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	23
Message-ID:	<87pes3$2l8$1@nets3.rz.RWTH-Aachen.DE>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000208093202 DOT 28790G-100000 AT is>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 950025923 2728 137.226.32.75 (8 Feb 2000 16:05:23 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	8 Feb 2000 16:05:23 GMT
User-Agent:	tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
[...]
> You could also create a batch file for each
> script FOO, called FOO.bat, which would say this:

> 	    @echo off
> 	    sh %0

> However, there's a caveat: you cannot redirect standard streams of a
> batch file, so if you go this way, you lose the ability to redirect
> the script's I/O, which might be important for some scripts.

If you want, there's a remedy for that, as well: *Compile* the batch
files to .com files, using PC Magazines 'Bat2exec'. Remarkably enough,
those compiled batch files do support redirection, unlike the
originals.

I used it, a *long* while ago, to set up a whole legion of such
compiled batches for the DJGPP port of NETPBM. Worked like a charm,
once I got it set up.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -