At 04:59p -0600 05/10/2006, Doug McNutt didst inscribe upon an
electronic papyrus:
At 17:25 -0400 5/10/06, Jim Correia wrote:
>BBEdit actually doesn't look in ~/.MacOSX/environment.plist. It
just uses the POSIX APIs to look at the environment. It doesn't
care where the inherited environmen
On 10 May 2006, at 15:01 , Andrew Jaffe wrote:
The problem seems to be that BBEdit does *NOT* look at $PATH, at
least as set in my .tchsrc, which indeed gives me the /usr/local/
bin/python executable from the shell. Instead, it appears to look
in environment.plist for a PATH variable (even wh
Dear Jim-
> The problem seems to be that BBEdit does *NOT* look at $PATH, at
> least as set in my .tchsrc, which indeed gives me the /usr/local/
> bin/python executable from the shell. Instead, it appears to look
> in environment.plist for a PATH variable (even when invoked with
> the bbedit com
At 17:25 -0400 5/10/06, Jim Correia wrote:
>On May 10, 2006, at 5:01 PM, Andrew Jaffe wrote:
>
>>The problem seems to be that BBEdit does *NOT* look at $PATH, at least as
>>set in my .tcshrc, which indeed gives me the /usr/local/ bin/python
>>executable from the shell. Instead, it appears to loo
On May 10, 2006, at 5:01 PM, Andrew Jaffe wrote:
The problem seems to be that BBEdit does *NOT* look at $PATH, at
least as set in my .tchsrc, which indeed gives me the /usr/local/
bin/python executable from the shell. Instead, it appears to look
in environment.plist for a PATH variable (even
I use it for a lot of python programming, and I've noticed that the
BBEdit actually uses the wrong python interpreter: I've python 2.3
in /usr/bin/python and python 2.4 in /usr/local/bin. Is there some
way I can tell it to use the latter for running and checking scripts?
Yours,
Andrew
On 5/9/06 6:30 PM, "Andrew Jaffe" <[EMAIL PROTECTED]> wrote:
> I use it for a lot of python programming, and I've noticed that the
> BBEdit actually uses the wrong python interpreter: I've python 2.3
> in /usr/bin/python and python 2.4 in /usr/local/bin. Is there some
> way I can tell it to use t
On May 10, 2006, at 7:59 AM, Gregory Ramsperger wrote:
The other option is to do:
$ sudo mv /usr/bin/python /usr/bin/python2.3
$ sudo ln -s /usr/local/bin/python /usr/bin/python
to rename the old python and replace it with the new. The second
line is probably not really needed, but you never
On 5/9/06 at 8:34 PM, Jim Correia <[EMAIL PROTECTED]> wrote:
> On May 9, 2006, at 7:30 PM, Andrew Jaffe wrote:
>
> > I've just started using BBEdit and it seems great so far.
> >
> > I use it for a lot of python programming, and I've noticed that the
> > BBEdit actually uses the wrong python
On May 9, 2006, at 7:30 PM, Andrew Jaffe wrote:
I've just started using BBEdit and it seems great so far.
I use it for a lot of python programming, and I've noticed that the
BBEdit actually uses the wrong python interpreter: I've python 2.3
in /usr/bin/python and python 2.4 in /usr/local/b
On 5/10/06 at 12:30 AM, Andrew Jaffe <[EMAIL PROTECTED]> wrote:
> I use it for a lot of python programming, and I've noticed that the
> BBEdit actually uses the wrong python interpreter: I've python 2.3 in
> /usr/bin/python and python 2.4 in /usr/local/bin. Is there some way I
> can tell it to us
Hi All,
I've just started using BBEdit and it seems great so far.
I use it for a lot of python programming, and I've noticed that the
BBEdit actually uses the wrong python interpreter: I've python 2.3
in /usr/bin/python and python 2.4 in /usr/local/bin. Is there some
way I can tell it to
12 matches
Mail list logo
