Subject: Adjusted rate of 2.99%

From: Obama Refi-Program Eligibility Update <[email-masked]>
Date: Tue, 08 Jul 2014 13:29:52 -0700

This is the Home Refi Plan Banks Dont want you to use....

Why You ask? Because......

1. You have the option to shop lenders other than your current mortgage holder
2. Your homes Loan-to-value (LTV) may be 80% to 125%

Banks will make more money if they keep middle-class Americans at the higher mortgage rate that they negotiated years ago, so they are putting pressure on the Government to reverse this program. 
 
By refinancing at shockingly low rates, homeowners can reduce their payments by as much as $4,095 each year.

View Your Updated Rate Here -> http://www.jobgasich.com/rate/changes/view.index
[RefId: Atompub-archive ]
Rate Generated on July 7, 2014

-
-
-
-
-
-
-
-
-

To stop further messages write  Updated Notifications Services
115 Hadley Way Counce, TN 38326 or visit http://www.jobgasich.com/ko34/fki3/dfmg38/fm3/ghu/67uj/4defh/jki8.krui

For portability beyond bash, $0 may not always be enough. You may need to substitute "type -p $0" to make this work if the command was found on the path.  you can only use type -p if the script is executable. This can also open a subtle hole if the script is executed using bash test2.sh and there is another script with the same name executable somewhere else.    but since the question is tagged bash and the hash-bang line explicitly mentions /bin/bash I'd say it's pretty safe to depend on bashisms.  but the problem with using dirname $0 is that if the directory is the current directory, you'll get .. That's fine unless you're going to change directories in the script and expect to use the path you got from dirname $0 as though it were absolute. To get the absolute path: pushd `dirname $0` > /dev/null, SCRIPTP`, popd > / Crowder I'm not sure sure dirname $0 is a problem if you assign it to a variable and then use it to launch a script like $dir/script.sh; I would imagine this is the u
 se case for this type of thing 90% of the time. ./script.sh would work fine. As I said, it's fine as long as your script using it doesn't change the current directory. If your script does, then you try to launch is meant to be in the same directory as the original, it's going to fail because you're no longer gives wrong result in sourced scripts (including bashrc)I always thought it was print working directory.Cool, this doesn't resolve symlinks, which is exactly what I was looking for.  But surely there's a better way to expand that path? Yes, you can use $(readlink -f "$0") to get full path in canonical form with all symlinks resolved. Solves tons of problems.  is different from $0 when you include one bash file into another using . or source.   Du Song Jul 21 '13 at 5:55