Apologies Chris.  I removed it but am out of town so will have to test next
week.  I appreciate all your help.  I'll let you know if that makes it go
away.


On Mon, May 20, 2013 at 1:04 PM, Chris Rees <[email protected]> wrote:

> You are not 'sure'.
>
> Please do not solicit help and claim that you know better-- I told you
> hours ago to remove . from your path.
>
> Chris
>
> On 20 May 2013 17:49, sindrome <[email protected]> wrote:
> > Fair enough but that's not the root of this problem I'm sure
> >
> >
> > On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen <[email protected]
> >wrote:
> >
> >> On Mon, May 20, 2013 at 6:45 PM, sindrome <[email protected]> wrote:
> >> > Clearly I'm not the only one with this problem.  Something is amending
> >> onto
> >> > the PATH and I'd like to get to the bottom of this.  I'm sure it will
> >> help a
> >> > lot of people.
> >>
> >> Well, start by taking the current directory ('.') out of your PATH.
> >> (It is bad, for a number of reasons).
> >>
> >> HTH
> >> --
> >> Regards,
> >> Torfinn Ingolfsen
> >> _______________________________________________
> >> [email protected] mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> To unsubscribe, send any mail to "[email protected]
> "
> >>
> > _______________________________________________
> > [email protected] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "[email protected]"
> >
>
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"

Reply via email to