Greetings, Mike Rushton! > Right ... the extension is a windows thing.
Not really. It's a human thing, that let you tell the intended meaning of the file at a glance. > Most of the bourne shell scripts i have come across have no extension. > Some have the Shebang line ... while others don't have it. Ones that not have it are scripts not intended for direct invocation (like these normally residing in /etc/default/*) > I am still in the planing stages ... I am not sure if I am going to use > an extension or not. > It might be a good idea to use .sh and then you would know that it is a > script. I'm using this little wrapper to start scripts by shebang line. -->8-------->8-------->8-------->8-------->8-------->8-------->8------ C:\Programs\CygWin\bin\cygwrap.sh #! /bin/sh if [ -z "$1" ]; then echo "No command given, breaking off." 1>&2 exit 1 fi CMDNAME="$( cygpath -au "$1")" shift env "$CMDNAME" $* -->8-------->8-------->8-------->8-------->8-------->8-------->8------ along with association $ assoc .pl .pl=unixshell.script $ assoc .sh .sh=unixshell.script (etc.) $ ftype unixshell.script unixshell.script="C:\Programs\Cygwin\bin\env.exe" /bin/cygwrap.sh "%1" %* -- WBR, Andrey Repin (anrdae...@yandex.ru) 06.02.2014, <02:08> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
