Re: Add search path to the cygwin.

[mike corbeil ordinary user account <mcorbeil at NetRevolution dot com>]

David Korn wrote:
> 
> >"Fu, Jack" wrote:
> >>
> >> I tried to add path using $ $PATH=/cygnus/include:$PATH.
> 
> >From: mike corbeil ordinary user account [mailto:mcorbeil@NetRevolution.com]
> 
> >      $PATH=/cygnus/include:$PATH
> >      export PATH
> >
> >      or
> >
> >      $PATH=$PATH:/cygnus/include
> >      export PATH
> 
>   PMFBI, but.... surely you mean
> 
>        PATH=/cygnus/include:$PATH
>        export PATH
> 
>  because if you put that first $ sign there, it expands the path, rather
> than treating it as a variable name, so if (for example) your path used to
> be /usr/bin:/bin, then what you've just typed to bash (after expansion) is
> 
>    /usr/bin:/bin=/cygnus/include:/usr/bin:/bin
> 
> which of course doesn't make a lot of sense to bash...


You're abs(right), David Korn.  I've worked with the Korn, Bourne, C,
and Bash shells, much less the buggy C shell, except when doing some
maintenance on scripts I didn't create, and for login shells.  (I wasn't
the sys. admin., either, though it's okay for a login shell - rotten for
programming, comparitively anyway.)

I ooops'd, and what's worse is that I even reviewed what I wrote.  I've
been looking at the screen for too many hours, too many nights and
days.  The eyes go "fuzzy", seeing whitespace instead of $.

Serves as possibly a good little tutorial for the person I was
responding to.  I never programmed or worked in Unix before learning how
to do so and have always had books at hand for reference, for what ever
I was doing, including yours for ksh work.  Perhaps I take that too much
for granted when answering a question, too.

Sorry for the error.

> 
>     hth,
>         DaveK
> --
>  "The secret of life is honesty and fair dealing. If you can fake that,
> you've got it made." -Groucho Marx