| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Some older versions of Bash seem to spit out "not found" errors for
command -v on stderr
|
| |
|
|
|
|
|
|
| |
I thought the $( ) syntax wasn't defined by POSIX, but it is, and it
works in basically every modern Bourne shell including dash and ksh. As
it's much more readable and easier to nest I'll prefer it here.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mostly for clarity reasons; using this syntax:
if [ condition ]; then
commands
fi
As opposed to:
if [ condition ]
then
commands
fi
Or:
[ condition ] && command
|
|
|
|
| |
Shouldn't refer to Bash stuff in Bourne shell profile
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Looks like older versions of Bash emit well-intended error messages if
the command is not found that newer ones don't
|
|
|
|
|
|
| |
Designed to be a quiet no-op on systems where keychain(1) is
unavailable, and not to bleat about missing keys, trying the three
default ones
|
|
|
|
| |
Mostly because git doesn't do empty dirs
|
|
* No longer using .bash_logout
* No longer using .bash_profile, using POSIX-compliant .profile
* instead; in particular, moved most of environment settings into
.profile
* Moved some of the separable functionality of both .profile and
.bashrc into subdirectories (some scripts shared, some not)
* Tidied implementation of ls/grep aliases
* Updated install script to reflect all of the above
|