• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: latest shell script puzzlements
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: latest shell script puzzlements


  • Subject: Re: latest shell script puzzlements
  • From: Barry Chern <email@hidden>
  • Date: Thu, 13 Jan 2005 04:58:11 -0500

in a missive of 1/13/05, Barry Chern was seen to expound:

Is this likely to be the origin of such an error, does Applescript care about non-existing files that it shouldn't? Or, is it possible it is offended by the specific enclosing folder, "usr/bin", for some reason? Or is it more likely a mis-directing error, and it's hard to get "if"s and variables (the "$" prefixed kind) to read correctly.

No, no, no. Why do I always decide to write after 3 a.m. It's not "usr/bin" at all, it's "usr/local/"
but, again, not sure that's the source of the error, anyway. (see previous message.)
_______________________________________________
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
References: 
 >Re: Passing arguments to the script from command line. (From: Andrew Oliver <email@hidden>)
 >Re: Passing arguments to the script from command line. (From: Brian Johnson <email@hidden>)
 >latest shell script puzzlements (From: Barry Chern <email@hidden>)

  • Prev by Date: Re: Applescript to read metadata of iMovie clips?
  • Next by Date: RE: Inconsistancy Between Do Shell Script and Terminal?
  • Previous by thread: latest shell script puzzlements
  • Next by thread: Re: Passing arguments to the script from command line.
  • Index(es):
    • Date
    • Thread