Porting Linux shell scripts

Well, these commands edit .plist files in your /Users/xyz/Library/Preferences folder. So, if you look at these files, you can look at these files and base your Terminal commands after these.

These are XML-based files, so you can view them in a more readable format if you open them in Xcode, which is available in the Mac App Store.

In the Terminal, the format for these is "defaults write PLIST_FILE KEY -TYPE VALUE" where the PLIST_FILE is the name of the file in the Preferences folder without the .plist, KEY is the key that you can see in Xcode, -TYPE is the type of key that you can find Xcode (and you can find if there is an abbreviation for that type by typing "defaults" into the terminal), and value is the value you wish to set the key at.

Here are some of the string types from the Terminal:

-string <string_value>
-data <hex_digits>
-int[eger] <integer_value>
-float  <floating-point_value>
-bool[ean] (true | false | yes | no)
-date <date_rep>
-array <value1> <value2> ...
-array-add <value1> <value2> ...
-dict <key1> <value1> <key2> <value2> ...
-dict-add <key1> <value1> ...

Bash only reads scripts by default in your home directory, or if they are missing in /etc. See Bash's documentation. If using OSX's Terminal.app then by default it reads ~/.bash_profile.

This is true of all bash on Linux or other OSes.

To read from another directory e.g. /opt/local/etc/bash_completion.d you have to edit your start up files to source (i.e. include) the files from there

The instructions for the script do not mention /opt/local/... which is a non standard location on any Unix. (by non-standard it is allowed to be used by third party packages but not defined what should be in there) They say

1. Copy this file to somewhere (e.g. ~/.git-completion.sh).

2. Add the following line to your .bashrc/.zshrc:

   source ~/.git-completion.sh
   

3. Consider changing your PS1 to also show the current branch, see git-prompt.sh for details.

The progit quote assumes you know bash. All it is saying is put the files from the first quote into a specific place if you want all users on the machine to use them and not in ~ where only the user installing it can see them. i.e. the point is multi user versus single user.

He also picks that path as nothing else uses it and you should not edit /etc files in OS X as Apple's OS upgrades could overwrite them so you need to choose another place. (I would have chosen something under /usr/local as there is where manually maintained scripts are meant to go).

~/.bashrc is the correct place to edit and add the source. See your other question and the bash manual for setting up ~/.bash_profile The bash suggested way is source .bashrc into .bash_profile. Note that on OS X using Terminal.app is not the one way of running shells so there can be sessions starting with .bashrc.