Comments on: Bash Coding Convention ../ http://blog.apokalyptik.com/2008/06/19/bash-coding-convention/ The random things that spew forth from my brain... Mon, 16 Jan 2012 18:43:29 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19620 By: Papucho http://blog.apokalyptik.com/2008/06/19/bash-coding-convention/comment-page-1/#comment-9559 Papucho Tue, 07 Dec 2010 15:27:56 +0000 http://blog.apokalyptik.com/?p=291#comment-9559 From Argentina, Thanks. From Argentina, Thanks.

]]> By: Matthew Tardiff http://blog.apokalyptik.com/2008/06/19/bash-coding-convention/comment-page-1/#comment-8331 Matthew Tardiff Tue, 10 Mar 2009 11:15:10 +0000 http://blog.apokalyptik.com/?p=291#comment-8331 It's interesting that I accidentially ran across this. A few months ago I was looking for a way to achieve this. I couldn't find anything at the time, so I came up with this solution: readonly SCRIPT_DIR="$( dirname "$( which "$0" )" )" My solution depends on bash 3.2 however, for the "which" builtin. It's interesting that I accidentially ran across this. A few months ago I was looking for a way to achieve this. I couldn't find anything at the time, so I came up with this solution:

readonly SCRIPT_DIR="$( dirname "$( which "$0" )" )"

My solution depends on bash 3.2 however, for the "which" builtin.

]]> By: Mike Brittain http://blog.apokalyptik.com/2008/06/19/bash-coding-convention/comment-page-1/#comment-7845 Mike Brittain Thu, 19 Jun 2008 13:17:05 +0000 http://blog.apokalyptik.com/?p=291#comment-7845 My bash is pretty rickety, and this is exactly the sort of thing I'm always trying to do. Very helpful tip. My bash is pretty rickety, and this is exactly the sort of thing I'm always trying to do. Very helpful tip.

]]>