chmod to make executable command

khock19 wrote:
and I get no errors. But then when I type todo.sh it returns

-bash: todo.sh: command not found

You don't have problem with chmod. The problem is that the directory containing that file isn't in your "path". You can see this by typing the command "echo $PATH" (without the quotes). There are three ways to deal with this: (1) Invoke that command this way: ./todo.sh . (That's what the "Quick Start Guide" for that script tells you to do in step 5.) That tells bash to look for that command in the current directory. (2) Presuming you're positioned in the directory where that script file is, add that directory to the path using this command: export PATH=`pwd`:$PATH . You'll have to invoke that command every time you launch a new Terminal session unless you update your bash profile to include a command to set the PATH automatically. (3) Put the file todo.sh in one of the directories that's already in the PATH, such as /usr/local/bin.

ls -l todo.sh
-rwxr-xr-x 1 you staff 277 Dec 17 15:21 todo.sh

The x's above indicate if the file has executable permissions. I'm thinking that chmod did add executable permissions, so most like you do not have the directory containing todo.sh in your PATH environment variable.

You can continue to use the "sh todo.sh" approach, or you can specify a path to the todo.sh

./todo.sh # assumes you are in the directory with todo.sh
# -OR-
$HOME/todo.sh # assumes todo.sh is in your home directory
# -OR-
/full/path/to/todo.sh

You could also modify the PATH environment variable and put the directory with todo.sh in your PATH.

You modify PATH in your .bash_profile (does not exist if you have not created one in the past), or the .profile (bash will choose .bash_profile over .profile, and .profile does not exist unless you created it in the past).

Modifying PATH would be done something like:

nano .bash_profile

and add

export PATH="$PATH:/full/path/to/the/directory"

ONLY You know what /full/path/to/the/directory containing todo.sh is.

Others have provided you with the correct answer.

I'll leave you with the following example...

$ ./x.sh 
-bash: ./x.sh: Permission denied
$ chmod +x x.sh
$ ./x.sh
Hi
$ ./y.sh
-bash: ./y.sh: No such file or directory
$ ls y.sh
ls: y.sh: No such file or directory 
$ y.sh
-bash: y.sh: command not found
$ cat x.sh
echo "Hi"
$ 

Note the different diagnostics.