first line of a BASH script

[Wally]

isn't it supposed to be

#!/bin/bash

so you can run the script without having to type './'

it won't work on mine.

[muggins]

Is the script executable?

Code: Select all

chmod +x script_name

[rhadon]

Code: Select all

#!/bin/bash

This in the first line means it's supposed to run in bash, instead of ash or something else.

[muggins]

Plus, the file script_name, will only run as script_name if it's in the executable search PATH. Probably simplest to copy it to /usr/bin.

[Moose On The Loose]

Plus, the file script_name, will only run as script_name if it's in the executable search PATH. Probably simplest to copy it to /usr/bin.

I put them in my-applications/bin

On puppy, my-applications/bin is in the search path and is nearly empty. As a result, it is easy to find the scripts I have made.

[stu90]

Plus, the file script_name, will only run as script_name if it's in the executable search PATH. Probably simplest to copy it to /usr/bin.

I put them in my-applications/bin

On puppy, my-applications/bin is in the search path and is nearly empty. As a result, it is easy to find the scripts I have made.

Yes i keep my scripts in the same place.

[amigo]

Calling a script using simply the program name requires the program/script to be executable. Calling them as an argument to the shell doesn't require them to be executable. Also, 'sourcing' them ( . path/to/script/or/program ) doesn't require them to be executable.

[Moose On The Loose]

Calling a script using simply the program name requires the program/script to be executable. Calling them as an argument to the shell doesn't require them to be executable. Also, 'sourcing' them ( . path/to/script/or/program ) doesn't require them to be executable.

I didn't know that it didn't need to have the "x" set.


The

Code: Select all

. /root/my-applications/moose/defaults

if test -e  /root/my-applications/moose/settings; then
  . /root/my-applications/moose/settings
  fi

. /root/my-applications/moose/make_gui
... etc ..]

Is a nice way to do scripts if you don't mind a small hit on speed but like to keep the source for some things in its own file. The bit with the defaults and the settings is very good for making an application remember the choices the user made last time and using them as the default the next time. You just compose the settings file before you exit and it is done.

[amigo]

The real advantage to 'sourcing' is that all environment variables are available to the sourced code, without having to export anything. And, anything set (variable values) by the sourced script are available to the main script. Executing external scripts as separate processes does neither. Also, when sourcing an external script, the sourced file doesn't need any shebang at all.

[Bruce B]

I guess it should be mentioned that script variables and functions persist when a script file is sourced.

~

[amigo]

"And, anything set (variable values) by the sourced script are available to the main script."

[Bruce B]

"And, anything set (variable values) by the sourced script are available to the main script."

True and while on the topic that's why I source Midnight Commander to run it. All my aliases are available to me.

I wonder how many people use Midnight Commander. I use as my only file manager. Except for Rox, when I want to view thumbnails for icons, xpm and other image files

I even removed Rox as the desktop manager. Just use JWM and its wallpaper features. One wallpaper for each desktop.

~