09-01-2012
cygwin executable shell scripts
Hello,
Cygwin will execute a shell script without turning on executable status on the file.
I want to force cygwin to be more like linux and not execute scripts directly on the command line unless changing mode to have executable status.
Is this possible?
Thanks
Larry
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I installed Cygwin y'day on Win XP SP2.
The install went fine but when I clicked on Cygwin's shortcut to invoke its shell, it didn't come up.....was just opening for a fraction of second and then closed.
Can anyone please advise?
Regards
er_ashu (6 Replies)
Discussion started by: er_ashu
6 Replies
2. Shell Programming and Scripting
I haven't been on a unix system in a long time and I'm trying to teach a friend unix. After looking at/testing various options cygwin seemed to be the easiest to download and install.
Everything works pretty much as I recall and I even tested a small java program on it.
I can't seem to get... (4 Replies)
Discussion started by: mmtemp
4 Replies
3. Shell Programming and Scripting
Hi all ,
I need to call an executable (.exe) using shell script.
Actual need is i need to call that shell script and do an export of some tables
is there any way . the executable is datamover
Please let me know if there are any option !! (2 Replies)
Discussion started by: raghav1982
2 Replies
4. Shell Programming and Scripting
I'm using cygwin under WinXP.
When I write things like ls > list.txt in shell, it works OK.
But when I place it to file like this:
It says that "list.txt" doesn't exists.
I tried touch, but the answer is the same. (2 Replies)
Discussion started by: TeenageWerewolf
2 Replies
5. Shell Programming and Scripting
hi,
I am using Cygwin for running the shell script.
If i execute the following command at the prompt output is obtained.
grep echo *
The same i have put in a file and when am trying to execute it is throwing error.
IP.sh
echo "Starting command..........."
grep echo *
... (9 Replies)
Discussion started by: flamingo_l
9 Replies
6. Shell Programming and Scripting
I would like to make a script that I can see if the file is executable. If it is executable then it needs to run. Otherwise, if it is not executable the file needs to be edited, and run agian.
I hope you understand what i mean. :)
Thanks for the netherlands (4 Replies)
Discussion started by: dennisbest85
4 Replies
7. UNIX for Dummies Questions & Answers
Hi!I'm new in this forum,also in shell scripting! :P
I'd like to help me with an issue!the project wants to make a variable with a directory(any) and then print all executable files of this directory,sorted by size!Thank you! (8 Replies)
Discussion started by: strawhatluffy
8 Replies
8. UNIX Desktop Questions & Answers
Hi Friends,
I have a shell script which does some operations etc, would it be possible to create an executable file out from this shell script? meaning the executable file is not editable, thus the source code will not be visible to other users for copyright reasons.
Please help, thanks! (1 Reply)
Discussion started by: kokoro
1 Replies
9. Programming
Ok I feel kind of stupid asking since it's been a while since I used an UNIX system but here goes. I recently installed the full CYGWIN on my Windows 7 machine. Seem like a nice package. So to test it out I did the basic hello world deal. It compiles just fine. But when I run it it crashed :(. So I... (4 Replies)
Discussion started by: g8rmark
4 Replies
10. Shell Programming and Scripting
I have a file with below format :
2013-05-20 hello
has done
2013-05-20 hi
000abc
abc
2013-05-21 thank you
I want the out put to be like this :
2013-05-20 hello has done
2013-05-20 hi 000abc abc
2013-05-21 thank you
What I could think of is something like this :
cat... (7 Replies)
Discussion started by: Sparta
7 Replies
LEARN ABOUT LINUX
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)