Shell Programming and Scripting

I have a bunch of bash functions in a folder (~/BASH) that I added to my $PATH so that I can call them from anywhere.
Yesterday I stripped the .sh extension from all of them so that I just type the function name without adding .sh every time. Some of the functions still work. Some of them don't unless I type "bash" first, like `bash function`.
Should I just put the extensions back on, or is there a configuration option that I can change?

Make sure you are on the BASH shell when you are calling those functions if they were designed specifically for only BASH. I dont think there is aconfiguration settings as such.


-Devaraj Takhellambam

$SHELL is /bin/bash
The file is executable.

But something weird is still happening.

If the file is names bashf I can run it with `bash bashf`.
If I try to run `bashf` then I get an error:
"bash: syntax error near unexpected token `newline'"
If I put the ".sh" extension back on, I can run it simply with `bashf.sh`.

I guess the only real problem is that I can't find the bug in my code. But I'm puzzled why the bug only shows up in 1 of 3 situations.
Maybe I should just include the code. All it does is create a new file with a shabang on the first line:

Code:

#!/usr/bin/env bash

if [ $# -eq 1 ]; then

  if [ -e $1 ]; then
    echo "File already exists. Overwrite? [y/n]";
    read cnfrm;
      if [ "$cnfrm" = "y" ]; then
        echo '' > /dev/null;
      else
        echo 'Cancelling';
        exit 1;
      fi
    fi

  echo "#!/usr/bin/env bash" > $1;
  vi $1;

else
  echo 'Usage: bashf filename';
  echo "Exiting";
  exit 1;
fi

Do you have another file called bashf lying around?

What is the output of:

Code:

type -a bashf bashf.sh

Replace the shebang with:

Code:

#!/bin/bash

Why would that make a difference?

(Apart from the fact that his bash executable may not be in /bin, in which case his shebang will work, yours will not.)