Hi Any Forums, oldfag from 2016 here, do I have to end Bash scripts with exit 0 every time...

Hi Any Forums, oldfag from 2016 here, do I have to end Bash scripts with exit 0 every time? And what's the deal with symlinking scripts to the /bin directory?

Attached: 1134920653.jpg (1680x1668, 309.61K)

Other urls found in this thread:

tldp.org/LDP/abs/html/exitcodes.html
twitter.com/NSFWRedditGif

>oldfag from 2016
kys
>do I have to end Bash scripts with exit 0 every time?
no
>what's the deal with symlinking scripts to the /bin directory?
retardation

based 2016 veteran

exit is only useful if you want to exit the shell immediately or return a non-zero on exit

armpits

>what's the deal with symlinking scripts to the /bin directory?
isn't it because thats one of the default search paths for bash to look for scripts? so you can just time "nigger" to invoke the script instead of "./nigger" for example

I see, so simply closing the shell/terminal manually after executing the script would have the same effect
I'm not sure but that does make sense. I see people talk about doing it to avoid having to manually edit the scripts when they're moved to different locations

Attached: 33920443152.jpg (1304x1440, 216.56K)

That's my catwife Kyaru right there, buddy. You better show some respect or I'm gonna post more pictures of her

Attached: 2349452657.jpg (1124x1440, 218.83K)

>simply closing the shell
yes, but I was mostly talking about exiting subshells within your scripts, this seems to completely fly over your head though

A well written script shouldn't need any changes if moved around, the positional variable $0 tells you the name of the executable name for the script.

You could use this internally, or make a script automatically enable certain features if called with a different name, like nano does.
It comes with a symbolic link rnano which points to nano.

Relative symlinks ARE sensitive to where they are placed and would have to be edited if they're not using absolute paths.

Exit codes are for debugging, mainly.

See: tldp.org/LDP/abs/html/exitcodes.html

>I see people talk about doing it to avoid having to manually edit the scripts when they're moved to different locations

If the script is local, it's best to put it in /home/$USER/.local/bin, adhering to the XDG Base Directory Specification.

/usr/bin is where you should place global scripts. If you're editing a script often, you can use a symlink, keeping the link somewhere in your home folder and the target in /usr/bin.