Mail Archives: djgpp/2000/12/20/15:59:42
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> > > > This is all good, except there shouldn't be a space after "PATH=", the
> > > > space will probably stop that command from taking effect.
> > >
> > > Actually, the space *after* the equals sign are ignored by
> > > COMMAND.COM. So this most probably is not the problem.
> > C:\>set PATH= C:\DJGPP\BIN;%PATH%
> > Too many parameters
> >
> > What did I do wrong here?
>
> Nothing. The point is that such a space will either produce the above
> error message, in which case C:\DJGPP\BIN won't be on the PATH
Which would be consistent with the error "Bad command or file name"
when rhide is run from the command line, right?
> (but we saw it was there),
I've re-read that post and I do not see it.
> > > > > Looking at my AUTOEXEC.BAT file from MS-DOS (as opposed to the edit
> > > > > screen), I noticed it has the line "set
> > > > > PATH=C:\DJGPP\BIN;C:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND" in place
> > > > > of the line "set PATH=C:\DJGPP\BIN;%PATH%". So even though I typed
> > > > > the line in right, I think it is having problems with it (though this
> > > > > may be normal for all I know).
> > > >
> > > > I don't think this is normal.
> > >
> > > Actually, it _is_ normal.
> >
> > That's useful to know. ;-) What is it that causes the line to change?
>
> The construct %PATH% is expanded to the previous value of PATH when
> the shell executes the "set PATH=" command.
Sorry, I'm obviously missing something here. How does the expanded
path find its way back into autoexec.bat?
- Raw text -