safe shell command

Ken Ray kray at sonsothunder.com
Fri Feb 21 16:41:01 CST 2003


Here's the full scoop:

1) The default path starts in the Rev directory (or wherever the MC
interpreter is running ). Let's say "C:\Program Files\Revolution\".

2) If you want to launch something in that directory, you just need to
provide the relative path (as Richard mentioned).

3) If you want to launch something in another directory, but *on the
same drive*, you can "cd" to the directory and use "start" on the item
in the directory, concatenated with a "&", as in:

  cd c:\program files\microsoft office\office10 & start winword.exe

4) If you want to launch something *on another drive*, you have to do it
in three stages: "cd" to the drive itself (optionally including the
drive letter), then "cd" to the directory, then "start" the file, as in:

  cd i:\ & cd i:\mystuff\launchfiles & start MyApp.exe

Just trying this:

  cd i:\mystuff\launchfiles & start MyApp.exe

when you're on the "C:" drive just won't work.

Hope this clears things up,

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/


----- Original Message -----
From: "Alex Rice" <alrice at arcplanning.com>
To: "Richard K. Herz" <herz at ucsd.edu>
Cc: <use-revolution at lists.runrev.com>
Sent: Friday, February 21, 2003 2:49 PM
Subject: Re: safe shell command


>
> On Friday, February 21, 2003, at 01:02  PM, Richard K. Herz wrote:
> >  If I'm understanding you right, a shell cd with the full pathname
has
> > problems of
> > potential path differences between Rev/MC and Windows.
> >
> I'm not sure about that. Just being paranoid :-) I encountered that
> problem on OS X with Rev <-> Javascript <-> shell commands.
>
> Alex Rice, Software Developer
> Architectural Research Consultants, Inc.
> alrice at ARCplanning.com
> alrice at swcp.com
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list