Basically, to "transfer" a value from one script (run) to another, you may want to store the value in question to a plain text file, e.g. by updating the "intro" of your script approximately as follows:
Hi,
I'm attempting to take the following input list and create an output file as shown below. I've monkeyed around for long enough. Can anyone help?
NOTE: fs*** will be header and I want to get a count on NY**.
fs200a
NY7A
fs200b
NY7B
NY7B
NY7B
fs200c
NY7C
NY7C
NY7C
NY7C... (2 Replies)
Date of Request: 20080514 10:37 Submitted By: JPCHIANG
i want to get the value "JPCHIANG" only in read a file, however, when i do this:
name=`"$line"|cut -d " " -f8`
it display all the line and append 'not found' at the end of the statement
the $line is actually a variable in a... (2 Replies)
Hi,
I've a data file with similar keys coming in. I want to assign an incremental counter to those records and attach to a file
for example
File
10001 ABCD
10002 PQRS
10001 ABCD
10003 QWER
10001 ABCD
10002 PQRS
10004 POIU
output as
10001 ABCD 1
10002 PQRS 1
10001 ABCD 2
10003... (3 Replies)
Hi All,
I have a problem assigning variables to script.I have a script in which i have a while loop now i have to assign some values obtained to an array which will be used later in the script.Can anyone help how to do that.
At present my scrot looks like:
co=0
pco=0
co=`cat /tmp/highcpu... (4 Replies)
suppose in my script i have written
a1=2
a2=4
read option
# I directly want to see the value of a1 or a2 (i:e; 1 or2 )depending upon i/p given like a1 or a2 to option var.so what should i give .Suppose if I give a1 to option then how can I see the value.
echo $$option --- doesn't work
pls... (3 Replies)
Hi
I have a file like below
############################################
# ParentFolder Flag SubFolders
Colateral 1 Source1/Checksum
CVA 1 Source1/Checksum
Flexing 1 VaR/Checksum
Flexing 1 SVaR/Checksum
FX 1 ... (5 Replies)
Hi,
This is the script that am trying to execute.
a= sar 1 5 | grep ^A | awk '{print $5}'
echo $a
i am getting output.
99
i get a blank space for echo $a.
Why is the value not getting assigned to a??
Thanks in Advance.
How to use code tags (6 Replies)
i having a file
xxxxxxxxxxxxxxx1234 ...........value can be change
xxxxxxxxxxxxxxx1235
xxxxxxxxxxxxxxxx1236
.
.
.
.
xxxxxxxxxxxxxxxxx1300 ...........value can be change
i want to cut last four characters of first line and last line and find the missing pattern.
output should... (4 Replies)
I am writing a bash script where I use two types of files that both contain a numerical pattern of the type 123.4567 (always groups of three and four digits separated by period) within their filenames. I need to assign the numerical patterns of these filenames to variables (inside a for loop),... (6 Replies)
Discussion started by: Mauve
6 Replies
LEARN ABOUT MOJAVE
osascript
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