Browse files

.bash_profile: Add `~/bin` to the `$PATH`

Just like before, the `$PATH` can still safely be extended by adding `~/.path`.
  • Loading branch information...
1 parent 7adb09c commit 0e28ec0e3b2e62f226667223ed7491ddb5b5a047 @mathiasbynens committed Aug 10, 2012
Showing with 7 additions and 4 deletions.
  1. +5 −2 .bash_profile
  2. +2 −2 README.md
View
7 .bash_profile
@@ -1,6 +1,9 @@
+# Add `~/bin` to the `$PATH`
+export PATH="$HOME/bin:$PATH"
+
# Load the shell dotfiles, and then some:
-# * ~/.path can be used to set or extend `$PATH`.
-# * ~/.extra can be used for settings you don’t want to commit.
+# * ~/.path can be used to extend `$PATH`.
+# * ~/.extra can be used for other settings you don’t want to commit.
for file in ~/.{path,bash_prompt,exports,aliases,functions,extra}; do
[ -r "$file" ] && source "$file"
done
View
4 README.md
@@ -36,10 +36,10 @@ To update later on, just run that command again.
If `~/.path` exists, it will be sourced along with the other files, before any feature testing (such as [detecting which version of `ls` is being used](https://github.com/mathiasbynens/dotfiles/blob/aff769fd75225d8f2e481185a71d5e05b76002dc/.aliases#L21-26)) takes place.
-Here’s an example `~/.path` file that adds `~/bin` to the `$PATH`:
+Here’s an example `~/.path` file that adds `~/utils` to the `$PATH`:
```bash
-export PATH="$HOME/bin:$PATH"
+export PATH="$HOME/utils:$PATH"
```
### Add custom commands without creating a new fork

0 comments on commit 0e28ec0

Please sign in to comment.