dotfiles.git - Personal scripts and configuration files

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Wrapper for pushd defaults to $HOME if no args	Tom Ryder	2013-08-20	1	-0/+5
\|
*	Alias cd directly rather than via alias	Tom Ryder	2013-08-20	1	-2/+1
\|
*	Better var names for subfile config sourcing	Tom Ryder	2013-08-20	1	-3/+3
\|
*	Fix a few variable contamination issues	Tom Ryder	2013-08-20	2	-0/+2
\|
*	More conservative expansion for dotfile paths	Tom Ryder	2013-08-20	2	-3/+3
\|
*	Turn off control character echo with stty	Tom Ryder	2013-08-20	1	-2/+2
\|
*	Remove trailing semicolon from sprunge function	Tom Ryder	2013-08-20	1	-1/+1
\|
*	Use better test for interactive shell	Tom Ryder	2013-08-20	1	-1/+1
\|
*	Remove unnecessary quoting in simple assignments	Tom Ryder	2013-08-20	4	-28/+26
\|
*	Remove unneeded quoting within [[ ]]	Tom Ryder	2013-08-20	6	-14/+14
\|
*	Use arithmetic expression for argument count	Tom Ryder	2013-08-19	1	-1/+1
\|
*	Merge integer declarations onto one line	Tom Ryder	2013-08-19	1	-2/+1
\|
*	Use arithmetic expressions in prompt function	Tom Ryder	2013-08-19	1	-2/+3
\|
*	Remove unnecessary quoting	Tom Ryder	2013-08-19	2	-2/+2
\|
*	Remove unnecessary variable bracing in .bashrc	Tom Ryder	2013-08-19	1	-2/+2
\|
*	Move --color option for grep to end of alias	Tom Ryder	2013-08-18	1	-7/+7
\|
*	Add some comments to the ls/grep alias functions	Tom Ryder	2013-08-18	2	-0/+24
\|
*	Use arithmetic expression for color space tests	Tom Ryder	2013-08-18	2	-2/+4
\|
*	Use arrays to collect options for ls/grep aliases	Tom Ryder	2013-08-18	2	-8/+9
\|
*	Use double-quoted printf strings for newlines	Tom Ryder	2013-08-18	1	-1/+1
\| \| \| \|	Just for clarity/syntax highlighting
*	Direct cd errors to stderr	Tom Ryder	2013-08-18	1	-1/+1
\|
*	Use arithmetic expansion for argument count test	Tom Ryder	2013-08-18	1	-1/+1
\|
*	Remove extraneous quoting	Tom Ryder	2013-08-18	1	-3/+3
\| \| \| \|	Overkill for expansions that will be integers by definition
*	Practicing writing half-decent Bash	Tom Ryder	2013-08-18	1	-4/+4
\| \| \| \| \|	Use array variable to collect options (appending with a pre-3.01 compatible syntax)
*	Test for substring presence in cd function	Tom Ryder	2013-08-05	1	-1/+6
\|
*	Quote expansions in cd function	Tom Ryder	2013-08-05	1	-2/+2
\|
*	Sort options alphabetically	Tom Ryder	2013-08-05	1	-1/+1
\|
*	Inline while loop in cd function with do	Tom Ryder	2013-08-05	1	-2/+1
\|
*	Initialise cd options to empty string	Tom Ryder	2013-08-05	1	-1/+2
\|
*	More thorough quoting	Tom Ryder	2013-08-05	2	-5/+5
\|
*	Avoid using builtin names for promptt function arg	Tom Ryder	2013-08-05	1	-3/+3
\|
*	Don't check for tput	Tom Ryder	2013-08-05	1	-19/+11
\| \| \| \|	It's specified by POSIX, so probably overkill
*	Improve quoting around expansions	Tom Ryder	2013-08-05	1	-14/+14
\|
*	Improve color detection logic for prompt/ls/grep	Tom Ryder	2013-08-05	3	-14/+26
\| \| \| \|	Use tput properly and only when found and necessary
*	Add sprunge script for my convenience	Tom Ryder	2013-08-04	1	-0/+6
\|
*	Restore stderr redirection for command -v	Tom Ryder	2013-08-02	3	-4/+4
\| \| \| \| \|	Some older versions of Bash seem to spit out "not found" errors for command -v on stderr
*	Combine conditionals in logout script	Tom Ryder	2013-07-31	1	-3/+2
\|
*	Improve comments on shell scripts	Tom Ryder	2013-07-31	3	-4/+57
\|
*	Trailing whitespace fixes	Tom Ryder	2013-07-31	1	-1/+1
\|
*	Speed up SVN prompt with only one call to svn info	Tom Ryder	2013-07-31	1	-5/+6
\| \| \| \| \|	Keep the output of `svn info` in a new local variable and use Bash herestrings to read the repository URL and root from that variable
*	Explicitly check for setup command existence	Tom Ryder	2013-07-31	2	-3/+9
\|
*	Stop ignoring error output from setup commands	Tom Ryder	2013-07-31	3	-4/+4
\|
*	Use standard structure for if/for in shell	Tom Ryder	2013-07-31	6	-38/+66
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Mostly for clarity reasons; using this syntax: if [ condition ]; then commands fi As opposed to: if [ condition ] then commands fi Or: [ condition ] && command
*	Place missing quotes	Tom Ryder	2013-07-30	2	-4/+4
\|
*	Fix grep/ls aliasing for efficiency/correctness	Tom Ryder	2013-07-30	2	-8/+8
\| \| \| \|	Avoiding the use of echo, using builtins whereever possible
*	Use clearer option name for dircolors call	Tom Ryder	2013-07-30	1	-1/+1
\|
*	Fix bug in ls color management	Tom Ryder	2013-07-30	1	-1/+1
\| \| \| \|	Ignoring output for an eval call? Real smart, Tom
*	Use integer declarations in prompt function	Tom Ryder	2013-07-30	1	-2/+2
\|
*	More portable non-surprise syntax for functions	Tom Ryder	2013-07-30	5	-5/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	<tyrmored> is this syntax actually problematic? <tyrmored> function whatever { <tyrmored> thangs <tyrmored> } <zendeavor> !pf function <greybot> http://mywiki.wooledge.org/BashPitfalls#pf25 -- Don't do this! -- function foo() <tyrmored> i know it's bashism, but is it bad practice <tyrmored> yeah i know that much <tyrmored> (no parens, that is) <zendeavor> it's not necessarily a bashism, but the function keyword has implications in other shells <zendeavor> and, perhaps someday in the future, for bash as well <tyrmored> hmm, so i should use this syntax even if the scripts are explicitly bash? <ffio> hi zendeavor :) <zendeavor> you should use foo() { echo bar; } <tyrmored> rightoh <zendeavor> no surprising behaviour that way, ever <tyrmored> makes sense <zendeavor> it won't matter much but element of least surprise
*	Dropped a newline	Tom Ryder	2013-07-21	1	-0/+1
\|