ealize that this approach may
be fragile in environments that you don't control (i.e. end-users). There also
may be other variables needed...
> Envoyé depuis Yahoo Mail pour iPad
>
> From: Keary Suska ;
> To: Colas B ;
> Cc: Cocoa-Dev (Apple) ;
> Subject: Re: NSTask: pro
On Apr 10, 2014, at 4:09 PM, Colas B wrote:
> No, it is "Mach-O 64-bit executable"
Then there is no shell run when you execute it via NSTask.
Really, the correct answer is that pdflatex should not depend on a relative or
hard-coded path for gnuplot. (It's fine of course to use such as a defaul
No, it is "Mach-O 64-bit executable"
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your
On Apr 10, 2014, at 2:34 PM, Colas B wrote:
> I don't specify explicitly a bash when I run my program (with NSTask) : I
> just give the path to the program.
It sounds like the program you’re telling NSTask to run is a shell-script. You
can easily verify that by using the ‘file’ command (or j
I am not an unix-ey guy... I don't specify explicitly a bash when I
run my program (with NSTask) : I just give the path to the program. If I
discover the path to the shell being used, does it mean that what used to be
the path of my NSTask will become an argument?About path and
environment var
On Apr 10, 2014, at 2:52 PM, Colas B wrote:
> Hi,
>
> thanks for your answers !
> Your idea sounds good. What can I do if I want both shells invoked from
> programs and login shells to have the same initialization script? Shall I
> write a new script that runs first ~/.login and then myprogram
On Apr 10, 2014, at 1:52 PM, Colas B wrote:
> Your idea sounds good. What can I do if I want both shells invoked from
> programs and login shells to have the same initialization script?
I think it’s better to make sure your login-shell setup script (.bash_profile
or .login) doesn’t have thing
Hi,
thanks for your answers !
Your idea sounds good. What can I do if I want both shells invoked from
programs and login shells to have the same initialization script? Shall I write
a new script that runs first ~/.login and then myprogram ? Or is there a
simplier way?
In my case, myprogram is
On Apr 10, 2014, at 6:23 AM, Keary Suska wrote:
> This is more likely a shell scripting issue, rather than am NSTask issue,
> unless sandboxing is somehow interfering, and you are obscuring the issue by
> not telling us at least how myprogram is locating myauxprogram. The most
> likely culpri
On Apr 10, 2014, at 6:57 AM, Colas B wrote:
> Dear cocoa-dev,
>
> I want to do with an `NSTask` what I am able to do in the terminal via
>
> $ myprogram myfile.ext
>
> I know that `myprogram` (I don't have any control on this program) launches
> another program `myauxprogram`. Furthermore,
Dear cocoa-dev,
I want to do with an `NSTask` what I am able to do in the terminal via
$ myprogram myfile.ext
I know that `myprogram` (I don't have any control on this program) launches
another program `myauxprogram`. Furthermore, the path to `myprogram` is `path1`
and the path to `myprogr
11 matches
Mail list logo
