fix sage-sage script

[dangrayson]

I think there is a superfluous "shift" in the "sage-sage" script, because this works:

$ sage -sh -c -c "echo hi there"

Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage!

Bypassing shell configuration files ...

hi there Exited Sage subshell.

but this doesn't:

$ sage -sh -c "echo hi there"

Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage!

Bypassing shell configuration files ...

bash: echo hi there: No such file or directory Exited Sage subshell.

--

$ sage --version | Sage Version 3.2.2, Release Date: 2008-12-18 |

[ddrake]

The patch at #4644 fixes this problem, according to this thread: ​http://groups.google.com/group/sage-devel/browse_thread/thread/384d4fe7dabb722c/

[mvngu]

With Sage 4.3.2.alpha1, I get:

[mvngu@mod sage-4.3.2.alpha1]$ ./sage -version
| Sage Version 4.3.2.alpha1, Release Date: 2010-01-31                |
* Warning: this is a prerelease version, and it may be unstable.     *
[mvngu@mod sage-4.3.2.alpha1]$ ./sage -sh -c -c "echo hi there"

Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!

Bypassing shell configuration files ...

hi there
Exited Sage subshell.
[mvngu@mod sage-4.3.2.alpha1]$ ./sage -sh -c "echo hi there"

Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!

Bypassing shell configuration files ...

hi there
Exited Sage subshell.

I'm closing this ticket as fixed by #4644.