Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Remove some overzealous command checks | Tom Ryder | 2014-10-13 | 1 | -5/+0 |
| | |||||
* | Remove overengineered tmux args array | Tom Ryder | 2014-10-10 | 1 | -7/+3 |
| | |||||
* | Correct inverted test | Tom Ryder | 2014-10-04 | 1 | -1/+1 |
| | |||||
* | Restructure tmux argument determination | Tom Ryder | 2014-10-04 | 1 | -8/+8 |
| | |||||
* | Allow specifying default tmux session name | Tom Ryder | 2014-09-28 | 1 | -3/+11 |
| | | | | Also restructure so only one explicit call to tmux command | ||||
* | Use space before semicolon as command separator | Tom Ryder | 2014-02-10 | 1 | -2/+2 |
| | |||||
* | Detach session on attaching by default | Tom Ryder | 2013-12-21 | 1 | -1/+1 |
| | |||||
* | Change null-arguments check for tmux func | Tom Ryder | 2013-12-21 | 1 | -2/+2 |
| | |||||
* | Check for presence of binaries before script setup | Tom Ryder | 2013-10-16 | 1 | -0/+5 |
| | |||||
* | Use tidier default system for tmux function | Tom Ryder | 2013-09-14 | 1 | -8/+6 |
| | |||||
* | Remove instances of error-prone &> redirection | Tom Ryder | 2013-09-01 | 1 | -1/+1 |
| | |||||
* | Restructure tmux wrapper function slightly | Tom Ryder | 2013-08-25 | 1 | -2/+2 |
| | |||||
* | Use arithmetic expression for argument count | Tom Ryder | 2013-08-19 | 1 | -1/+1 |
| | |||||
* | Improve comments on shell scripts | Tom Ryder | 2013-07-31 | 1 | -0/+6 |
| | |||||
* | More portable non-surprise syntax for functions | Tom Ryder | 2013-07-30 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | <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 | ||||
* | Use correct Bash arguments expansion | Tom Ryder | 2013-06-23 | 1 | -2/+2 |
| | |||||
* | Massive overhaul of structure for Bash files | Tom Ryder | 2013-06-20 | 1 | -0/+9 |
* 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 |