03-20-2010
Need help writing an Applescript to launch a specific Terminal Command...
I developed a script in Lingon (which is an automated script editor developed for OS X) that is used to automatically restart programs only if they crash. The script itself does just that, but I only want it to load if I'm going to use the specific application that it's designed to protect. In the OS X Terminal, when I type these two commands consecutively:
launchct1 unload "/Users/ME/Documents/Backed Files 2/Automator/Scripts/com.Restart.PROGRAM.Lingon.plist"
*ENTER*
launchct1 load "/Users/ME/Documents/Backed Files 2/Automator/Scripts/com.Restart.PROGRAM.Lingon.plist"
*ENTER*
My program immediately launches and, since I'll keep it running for several weeks, will always relaunch if it crashes. The problem is that I'm trying to create an Applescript (Shell Script) command that would incorporate these two previous commands in order for me to be able to launch it by way of double clicking my new script, as opposed to having to manually type these commands in the terminal and keep the terminal window open whenever I want to run my longterm program as a project. I'd assume that it would look something like this:
do shell script
{launchct1 unload "/Users/ME/Documents/Backed Files 2/Automator/Scripts/com.Restart.PROGRAM.Lingon.plist";
launchct1 unload "/Users/ME/Documents/Backed Files 2/Automator/Scripts/com.Restart.PROGRAM.Lingon.plist"}
but that doesn't work. I've tried to execute similar code into my Applescript using the Automator in order to test the shell script but everytime I run the changes it also reports an error. Any suggestions?
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am a newbie here. Trying to find a way of writing a script to launch multiple terminal or console windows on solaris 9. I used to be able to do this using cmdtool on older versions of solaris and it was even possible to configure the size and screen position of the window and the title. ... (5 Replies)
Discussion started by: omerta
5 Replies
2. Shell Programming and Scripting
I am running Mac OS X (10.5). I run the following script successfully in terminal in order to split an mp3 file into 3 smaller mp3 files...
split -b 8667k -a1 Monday.mp3 Levin-Hour_; ls Lev* | sed "s/.*/mv '&' '&.mp3'/g" | zsh
However, when I run a similar script within the Applescript editor... (2 Replies)
Discussion started by: tgaleza
2 Replies
3. OS X (Apple)
I developed a script in Lingon (which is an automated script editor developed for OS X) that is used to automatically restart programs only if they crash. The script itself does just that, but I only want it to load if I'm going to use the specific application that it's designed to protect. In the... (2 Replies)
Discussion started by: JFraser1
2 Replies
4. Shell Programming and Scripting
Hello,
I have a PERL-TK based GUI from which I want to launch a command on an existing UNIX terminal (this is also the parent terminal for this perl based gui window). The command I want to launch is interactive (there is no intention to interact with that command from the same PERL gui i.e. no... (2 Replies)
Discussion started by: AnuragJindal
2 Replies
5. OS X (Apple)
What I want my script to do is to run a command in Terminal and close that same Terminal window when the process is complete.
Of course I could ad a delay of 6 seconds to complete the process, but it may not be enough every time.
To simplify my question, this is what I want to achieve.... (9 Replies)
Discussion started by: ShadowofLight
9 Replies
6. OS X (Apple)
After I installed OS X Lion I haven't been able to launch x11 remotely (using ssh) from Terminal.
It works fine locally, and also remotely directly from the Xterm.
I log in to the unix server at my university from the terminal like this:
ssh -l -X login@host.com
This used to launch... (1 Reply)
Discussion started by: gnyrf
1 Replies
7. Shell Programming and Scripting
I'm new using Unix commands in applescript. The following script you choose different folders with PDfs, get file count of PDfs on chosen folders, & write the results in text file.
set target_folder to choose folder with prompt "Choose target folders containing only PDFs to count files" with... (0 Replies)
Discussion started by: nellbern
0 Replies
8. Red Hat
After installing centos iam not able to see the terminal icon in the applications menu to launch the command prompt in Centos.
However iam able to see the Open Terminal menu, when i right click and it is not working.
let me know what are the things i need to check.:b: (1 Reply)
Discussion started by: Kesavan
1 Replies
9. Shell Programming and Scripting
The following command works perfectly in Terminal, but not in Applescript. (Returns "unknown token" error for square brackets.)
(new to site. sorry.)
I have an Applescript that is designed to find and remove any square-bracketed text, including the square brackets.
I ran the following code from... (1 Reply)
Discussion started by: Phillip Acosta
1 Replies
10. Shell Programming and Scripting
I have been having an extremely annoying problem. For the record, I am relatively new at this. I've only been working with unix-based OS's for roughly two years, mostly Xubuntu and some Kali. I am pretty familiar with the BASH language, as that's the default shell for debian. Now, I've made this... (16 Replies)
Discussion started by: Huitzilopochtli
16 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)