This is because the executable files under ~/bin/ are not always included in the path environment variable. Some distributions like Debian and derivatives do it this way, if you create the bin folder, but for other distributions you may have to add it to the path manually.
Or you can add ~/bin/ to your path editing .bashrc or other terminal initialization script, and using the next configuration lines:
PATH=~/bin:"${PATH}" export PATH
I have actually modified the configuration to use .bin (with the dot), because I do not like the bin folder showing in my beautifully organized home folder...
Comment
Just a little cent.
If the system can not found the script in ~/bin/ , the script invocation should be like:
$ cat ~/myfile | ~/bin/hastebinit
$ ~/bin/hastebinit < ~/myfile
$ ~/bin/hastebinit ~/myfile myotherfile
This is because the executable files under ~/bin/ are not always included in the path environment variable. Some distributions like Debian and derivatives do it this way, if you create the bin folder, but for other distributions you may have to add it to the path manually.
Or you can add ~/bin/ to your path editing .bashrc or other terminal initialization script, and using the next configuration lines:
PATH=~/bin:"${PATH}"
export PATH
I have actually modified the configuration to use .bin (with the dot), because I do not like the bin folder showing in my beautifully organized home folder...