Changes between Initial Version and Version 25 of Ticket #11790
 Timestamp:
 Mar 9, 2012, 4:18:12 PM (11 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

Ticket #11790

Property
Status
changed from
new
toneeds_review

Property
Authors
changed from
to
John Palmieri
 Property Cc Ivan Andrus added

Property
Priority
changed from
minor
toblocker

Property
Reviewers
changed from
to
Jeroen Demeyer

Property
Status
changed from

Ticket #11790 – Description
initial v25 18 18 And it's inconvenient if one wants to further process the output of some command run in a Sage subshell. 19 19 20 In ` local/bin/sagesage`, we have:20 In `spkg/bin/sage`, we have: 21 21 {{{ 22 22 #!sh … … 46 46 }}} 47 47 48 So I'd propose to change `sage sage` to not print ''any'' messages if the first argument to the subshell is `c`.48 So I'd propose to change `sage` to not print ''any'' messages if there are any further arguments to `sage sh`. 49 49 50 50 Alternatively, 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. … … 56 56 }}} 57 57 58 (Actually, `exec` should be used in a couple of Sage commands which don't need any "postprocessing", e.g. by `sagesage`.) 58 (Actually, `exec` should be used in a couple of Sage commands which don't need any "postprocessing", e.g. by `sage`.) 59 60 '''Apply''' [attachment:11790_sage_sh.patch] to the SAGE_ROOT repository.