09-09-2011
In general, you should seek help regarding AppleScript from AppleScript related sites. Likewise, Ruby from Ruby, Python from python...
The unix.com forums are primarily targeting command line scripting issues, involving shell commands one might use in bash, ksh, sh, and the like.
But, to your specific AppleScript issue, in the post containing "sorry here is my code fully" change the line that tests for "Prodcution" to this:
if theQuestion contains "Prodcution" then
No need to set another variable to the contents of theQuestion.
When you lack feedback from AppleScripts, create your own.
display dialog "You chose " & theQuestion
I'm a bit rusty on the ol' applescript. Sorry.
9 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Our Admin, Neo, has some experience with the subject of this news item:
http://news.com.com/2100-1016-1015814.html
It appears that The Open Group is suing Apple for using the term Unix without licensing from The Open Group. (3 Replies)
Discussion started by: auswipe
3 Replies
2. UNIX for Dummies Questions & Answers
When running our UNIX job scripts we randomly get the following 198 error below. When we restart the job it works fine. I haven't been able to recreate the problem in test, so I'm wondering if it has something to do with Cron or possibly a memory error or memory leak. I don't see anything... (5 Replies)
Discussion started by: rthiele
5 Replies
3. Shell Programming and Scripting
Hi everyone,
Looking for a suggestion to improve the below script in which I´ve been working.
The thing is I have 3 separated AWK scripts that I need to apply over the inputfile, and for scripts (2) and (3) I have to use a "temp" file as their inputfile (inputfile_temp and inputfile_temp1... (2 Replies)
Discussion started by: cgkmal
2 Replies
4. Shell Programming and Scripting
Hi folks
I use a Solaris 10 box with Bash shell.
I have here a script (it works!) to list all scripts in crontab which contains the string "sqlplus":
for i in $(ls `crontab -l | grep -v '#' | awk '{ print $6 }' | grep -v '^$'`); do grep -l 'sqlplus' "$i"; done
Is there a more elegant... (1 Reply)
Discussion started by: slashdotweenie
1 Replies
5. Ubuntu
Hi,
I'm using a Ubuntu Server 10.04 LTS and it works like a charm, except for the regular crontab.
Onde day a user had some problems with crontab, i analyse it and i see no problemns, all my stuff is working right. Cron is running smoth...
I only noticed it when i altered a script already... (2 Replies)
Discussion started by: grafman
2 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
We have an archiving script on our applications box. It is scheduled to run at 36th minute every hour.
36 * * * * /archive_7.sh
But it throws an error saying "sh: /archive_7.sh: not found". I am not able to understand why.
# ls -l /archive_7.sh ; file /archive_7.sh
-rwxr-xr-x ... (4 Replies)
Discussion started by: satish51392111
4 Replies
7. Shell Programming and Scripting
I want to print any matching IP addresse in List1 with List 2;
List 1
List of IP addresses;
161.85.58.210
250.57.15.129
217.23.162.249
74.76.129.101
30.221.177.237
3.147.200.59
170.58.142.64
127.65.109.33
150.167.242.146
223.3.20.186
25.181.180.99
2.55.199.32 (3 Replies)
Discussion started by: lewk
3 Replies
8. UNIX for Dummies Questions & Answers
I have found code like
exec 9<filename a number of times when looking over commonly used scripts here. What all does this do? Sometimes the filename is simply a list, but seems to always have read/write/execute attributes for all. I think the "<" means to accept this as input, but don't know... (3 Replies)
Discussion started by: wbport
3 Replies
9. Shell Programming and Scripting
Hi All ,
I need to create a scheduling capability on one of Linux boxes so that i could some 6 scripts back to back after a gap a given time difference .
To run script1 :-- my test1.sh for 3 hrs , followed by 2nd script ,mytest2.sh for 10 hrs , then mystest3.sh for 2 hrs , then... (3 Replies)
Discussion started by: Anamica
3 Replies
LEARN ABOUT NETBSD
npm-run-script
NPM-RUN-SCRIPT(1) NPM-RUN-SCRIPT(1)
NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)