Python wrote:
On 16 mrt 2009, at 22:15, Lou Pecora wrote:
Because the shell process in the Terminal window would exit right after
it started even when I was just trying to open a new window (not even
running a script), i.e. command-N in Terminal. So I could not run
anything from the Terminal.
On 16 mrt 2009, at 22:15, Lou Pecora wrote:
In article ,
Python wrote:
--
why don't you just execute the script directly form the terminal?
then you will be able to read all error messages...
and you can delete all the files you want
just my 2c
Arno
Because the shell process in the Term
Python wrote:
On 16 mrt 2009, at 22:10, Lou Pecora wrote:
why don't you just execute the script directly form the terminal?
then you will be able to read all error messages...
and you can delete all the files you want
just my 2c
Arno
Because the shell process in the Terminal window would
In article ,
Python wrote:
> > --
> why don't you just execute the script directly form the terminal?
> then you will be able to read all error messages...
> and you can delete all the files you want
>
> just my 2c
>
> Arno
Because the shell process in the Terminal window would exit right aft
On 16 mrt 2009, at 22:10, Lou Pecora wrote:
why don't you just execute the script directly form the terminal?
then you will be able to read all error messages...
and you can delete all the files you want
just my 2c
Arno
Because the shell process in the Terminal window would exit right
a
On 16 mrt 2009, at 18:21, Lou Pecora wrote:
Since this happened with a Python script and some people here use OS X
and Terminal to run scripts I thought this might be helpful.
I recently ran into this problem using Terminal and found the
solution.
I thought those who use the Terminal in OS
