Re: Passing calls to an AS app via shell?
Re: Passing calls to an AS app via shell?
- Subject: Re: Passing calls to an AS app via shell?
- From: "Adam K. Wuellner" <email@hidden>
- Date: Fri, 8 Oct 2004 13:02:39 -0500
On Oct 8, 2004, at 12:47 PM, Johnny AppleScript wrote:
I can write to any folder in that directory that does not have a space
in
the name; if I remove the space from the very same folder, echo (when
using
~ in the path) writes just fine; when I use the full path without the
tilde,
it works fine even with spaces (as long as they are properly escaped or
quoted).
Just a general observation that may be related:
When using tab completion in Terminal.app, if the path contains
characters that must be quoted, the ~ gets converted to the actual path
to the user's home directory. However, if the path contains no spaces,
the ~ remains in the tab-completed path on the CL.* There must be a
reason for this, and I would guess it's also the reason that you have
to forego using the ~ in the same circumstances in AS's do shell
script.
* In case the explanation is unclear, try the following:
In your home folder, create two new folders. Name the first "oneword",
and the second "two words". Open Terminal, and type:
ls ~/onew
then press the tab key. If you have no other folders beginning with
"onew" your command line should now have
ls ~/oneword/
Press return to run the command or control-U to clear the line. Now,
type
ls ~/two
and press tab. If you have no other folders beginning with "two" your
command line should now have
ls /Users/username/two\ words/
Maybe someone else can explain why this happens.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden