On 2012-01-29 22:29, Keshav Kini wrote: > On Mon, Jan 30, 2012 at 05:27, Keshav Kini <keshav.k...@gmail.com> wrote: >> Hmm. Indeed, `sage -sh -c gap -b` still displays a banner, for >> example, whereas `sage -gap -b` does not. `sage -sh -c gap -- -b` >> doesn't work either. `sage -sh -c 'gap -b'` does, though, so that's a >> workaround. The question then becomes, would we want `sage -C` to be >> consistent with `sh -c`, or would we want it to be consistent with how >> `sage -gap` et al. work currently? I would be fine with the latter >> (say, wrapping $@ into a single argument to the -c of the subshell). > > Er, I should mention that this -C option should be handled by the thin > bash script, of course - it doesn't make sense to start Python and > load argparse just to open a subshell! :) And -C is one of the useful options even when Sage has not been built completely, so we should not rely on Python for this -C option.
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
