1) is "open" part of the shell or an executable itself?
I'm writing a XUL application that launches another application on
windows using:
C:\WINDOWS\system32\cmd.exe /c start saluton.pho
I want this to work on Mac OS (10) as well, but don't have such a
machine myself (!). I think "open" is the equivalent of "start", so to
get this to work I need either:
/fullpath/open saluton.pho
or something like
/fullpath/someshell -c saluton.pho
So my questions are:
1) is "open" part of the shell or an executable itself?
2) where does "open" live (it's full path), or where is the shell (and
is /fullpath/someshell -c myfile correct)
Hi,
I'm writing a XUL application that launches another application on
windows using:
C:\WINDOWS\system32\cmd.exe /c start saluton.pho
I want this to work on Mac OS (10) as well, but don't have such a
machine myself (!). I think "open" is the equivalent of "start", so to
get this to work I need either:
/fullpath/open saluton.pho
or something like
/fullpath/someshell -c saluton.pho
So my questions are:
1) is "open" part of the shell or an executable itself?
2) where does "open" live (it's full path), or where is the shell (and
is /fullpath/someshell -c myfile correct)
C:\WINDOWS\system32\cmd.exe /c start saluton.pho
1) is "open" part of the shell or an executable itself?
2) where does "open" live (it's full path),
where is the shell
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 814 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 44:45:57 |
| Calls: | 13,529 |
| Calls today: | 7 |
| Files: | 5,294 |
| D/L today: |
2 files (1,007K bytes) |
| Messages: | 612,278 |