Opened 14 years ago
Closed 13 years ago
#5507 closed defect (fixed)
fix sage-sage script
Reported by: | dangrayson | Owned by: | was |
---|---|---|---|
Priority: | minor | Milestone: | sage-4.1.2 |
Component: | user interface | Keywords: | sage-sage |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
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 |
Change History (3)
comment:1 Changed 14 years ago by
Milestone: | → sage-3.4.1 |
---|
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
Milestone: | sage-4.3.2 → sage-4.1.2 |
---|---|
Report Upstream: | → N/A |
Resolution: | → fixed |
Status: | new → closed |
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.
The patch at #4644 fixes this problem, according to this thread: http://groups.google.com/group/sage-devel/browse_thread/thread/384d4fe7dabb722c/