From:	M DOT A DOT Bukin AT inp DOT nsk DOT su
To:	djgpp AT delorie DOT com
Subject:	Re: Newbie question: program does nothing under bash
References:	<sFhndAA3Cwv2EwcE AT tqbase DOT demon DOT co DOT uk>
Date:	09 Feb 1999 20:20:37 +0600
In-Reply-To:	David Allsopp's message of "Mon, 8 Feb 1999 15:20:23 +0000"
Message-ID:	<20socfpsjt.fsf@Sky.inp.nsk.su>
Lines:	37
X-Mailer:	Gnus v5.5/Emacs 19.34
Reply-To:	djgpp AT delorie DOT com

David Allsopp <daa AT tqSPAMbase DOT demon DOT co DOT uk> writes:

> Fine, compiled first time even :-).  However, it only runs under an MS-
> DOS command.com window (W95).
> 
> I have the GNU Unix utilities (grep, sed, awk, etc.), and generally work
> in a "bash" window.  If I try to run the program from bash, nothing
> happens.  I made the simple change of opening a file and writing a
> string out to that, in case there are stdout/stderr problems, but the
> program just seems to do nothing: no file is created.  Again, if I run
> this from command.com, the file is created OK.

Maybe you did not run it correctly.  You can run programs from current
directory even if you don't have current directory in the PATH, for
example

bash> ./test

will run program `test' (maybe with .exe, .bat or whatever) from
current directory.  On the other hand, if you do just

bash> test

it will run bash's built-in `test' command which will say nothing.

You can place current directory on the PATH, like this

bash> export PATH=$PATH:.

but, IMHO, it is better to use `./' to make it clear which program you
want to run (also, for true Unix accounts there are security reasons
not to put current directory in the PATH).

HTH,

-- 
Michael Bukin

- Raw text -