Changes between Initial Version and Version 25 of Ticket #11790


Ignore:
Timestamp:
Mar 9, 2012, 4:18:12 PM (11 years ago)
Author:
Jeroen Demeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11790

    • Property Status changed from new to needs_review
    • Property Authors changed from to John Palmieri
    • Property Cc Ivan Andrus added
    • Property Priority changed from minor to blocker
    • Property Reviewers changed from to Jeroen Demeyer
  • Ticket #11790 – Description

    initial v25  
    1818And it's inconvenient if one wants to further process the output of some command run in a Sage subshell.
    1919
    20 In `local/bin/sage-sage`, we have:
     20In `spkg/bin/sage`, we have:
    2121{{{
    2222#!sh
     
    4646}}}
    4747
    48 So I'd propose to change `sage-sage` to not print ''any'' messages if the first argument to the subshell is `-c`.
     48So I'd propose to change `sage` to not print ''any'' messages if there are any further arguments to `sage --sh`.
    4949
    5050Alternatively, all (or a reduced set of) messages should at least go to `stderr` instead of `stdout`, perhaps regardless of whether `-c` was specified or not.
     
    5656}}}
    5757
    58 (Actually, `exec` should be used in a couple of Sage commands which don't need any "post-processing", e.g. by `sage-sage`.)
     58(Actually, `exec` should be used in a couple of Sage commands which don't need any "post-processing", e.g. by `sage`.)
     59
     60'''Apply''' [attachment:11790_sage_sh.patch] to the SAGE_ROOT repository.