osacompile(1) [mojave man page]

OSACOMPILE(1)						    BSD General Commands Manual 					     OSACOMPILE(1)

NAME

     osacompile -- compile AppleScripts and other OSA language scripts

SYNOPSIS

     osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]

DESCRIPTION

     osacompile compiles the given files, or standard input if none are listed, into a single output script.  Files may be plain text or other
     compiled scripts.	The options are as follows:

     -l language
	   Override the language for any plain text files.  Normally, plain text files are compiled as AppleScript.

     -e command
	   Enter one line of a script.	Script commands given via -e are prepended to the normal source, if any.  Multiple -e options may be given
	   to build up a multi-line script.  Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
	   single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
	   shell intact.

     -o name
	   Place the output in the file name.  If -o is not specified, the resulting script is placed in the file ``a.scpt''.  The value of -o
	   partly determines the output file format; see below.

     -x    Save the resulting script as execute-only.

     The following options are only relevant when creating a new bundled applet or droplet:

     -s    Stay-open applet.

     -u    Use startup screen.

     -a arch
	   Create the applet or droplet for the specified target architecture arch.  The allowable values are ``ppc'', ``i386'', and ``x86_64''.
	   The default is to create a universal binary.

     The following options control the packaging of the output file.  You should only need them for compatibility with classic Mac OS or for cus-
     tom file formats.

     -d    Place the resulting script in the data fork of the output file.  This is the default.

     -r type:id
	   Place the resulting script in the resource fork of the output file, in the specified resource.

     -t type
	   Set the output file type to type, where type is a four-character code.  If this option is not specified, the creator code will not be
	   set.

     -c creator
	   Set the output file creator to creator, where creator is a four-character code.  If this option is not specified, the creator code will
	   not be set.

     If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.

     If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
     create.  If the filename ends with ``.app'', it creates a bundled applet or droplet.  If the filename ends with ``.scptd'', it creates a bun-
     dled compiled script.  Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.

EXAMPLES

     To produce a script compatible with classic Mac OS:

	   osacompile -r scpt:128 -t osas -c ToyS example.applescript

SEE ALSO

     osascript(1), osalang(1)

Mac OS X							 November 12, 2008							  Mac OS X

OSASCRIPT(1)						    BSD General Commands Manual 					      OSASCRIPT(1)

NAME

     osascript -- execute OSA scripts (AppleScript, JavaScript, etc.)

SYNOPSIS

     osascript [-l language] [-i] [-s flags] [-e statement | programfile] [argument ...]

DESCRIPTION

     osascript executes the given OSA script, which may be plain text or a compiled script (.scpt) created by Script Editor or osacompile(1).  By
     default, osascript treats plain text as AppleScript, but you can change this using the -l option.	To get a list of the OSA languages
     installed on your system, use osalang(1).

     osascript will look for the script in one of the following three places:

     1.   Specified line by line using -e switches on the command line.

     2.   Contained in the file specified by the first filename on the command line.  This file may be plain text or a compiled script.

     3.   Passed in using standard input.  This works only if there are no filename arguments; to pass arguments to a STDIN-read script, you must
	  explicitly specify ``-'' for the script name.

     Any arguments following the script will be passed as a list of strings to the direct parameter of the ``run'' handler.  For example, in
     AppleScript:

	   a.scpt:
	   on run argv
	       return "hello, " & item 1 of argv & "."
	   end run

	   % osascript a.scpt world
	   hello, world.

     The options are as follows:

     -e statement
	   Enter one line of a script.	If -e is given, osascript will not look for a filename in the argument list.  Multiple -e options may be
	   given to build up a multi-line script.  Because most scripts use characters that are special to many shell programs (for example,
	   AppleScript uses single and double quote marks, ``('', ``)'', and ``*''), the statement will have to be correctly quoted and escaped to
	   get it past the shell intact.

     -i    Interactive mode: osascript will prompt for one line at a time, and print the result, if applicable, after each line.  Any script sup-
	   plied as a command argument using -e or programfile will be loaded, but not executed, before starting the interactive prompt.

     -l language
	   Override the language for any plain text files.  Normally, plain text files are compiled as AppleScript.

     -s flags
	   Modify the output style.  The flags argument is a string consisting of any of the modifier characters e, h, o, and s.  Multiple modi-
	   fiers can be concatenated in the same string, and multiple -s options can be specified.  The modifiers come in exclusive pairs; if con-
	   flicting modifiers are specified, the last one takes precedence.  The meanings of the modifier characters are as follows:

	   h  Print values in human-readable form (default).
	   s  Print values in recompilable source form.

	      osascript normally prints its results in human-readable form: strings do not have quotes around them, characters are not escaped,
	      braces for lists and records are omitted, etc.  This is generally more useful, but can introduce ambiguities.  For example, the
	      lists '{"foo", "bar"}' and '{{"foo", {"bar"}}}' would both be displayed as 'foo, bar'.  To see the results in an unambiguous form
	      that could be recompiled into the same value, use the s modifier.

	   e  Print script errors to stderr (default).
	   o  Print script errors to stdout.

	      osascript normally prints script errors to stderr, so downstream clients only see valid results.	When running automated tests, how-
	      ever, using the o modifier lets you distinguish script errors, which you care about matching, from other diagnostic output, which
	      you don't.

SEE ALSO

     osacompile(1), osalang(1), AppleScript Language Guide

HISTORY

     osascript in Mac OS X 10.0 would translate '
' characters in the output to '
' and provided c and r modifiers for the -s option to change
     this.  osascript now always leaves the output alone; pipe through tr(1) if necessary.

     Prior to Mac OS X 10.4, osascript did not allow passing arguments to the script.

Mac OS X							  April 24, 2014							  Mac OS X