#12263: Unset TERM when running sage non-interactively
---------------------------------------------------------+------------------
Reporter: jdemeyer | Owner: leif
Type: defect | Status:
closed
Priority: major | Milestone:
sage-4.8
Component: scripts | Resolution:
fixed
Keywords: | Work_issues:
Upstream: Workaround found; Bug reported upstream. | Reviewer:
Volker Braun
Author: Jeroen Demeyer | Merged:
sage-4.8.rc0
Dependencies: |
---------------------------------------------------------+------------------
Comment(by jdemeyer):
Replying to [comment:5 leif]:
> Unsetting `TERM` unfortunately doesn't ''"effectively disable
readline"'', but may trigger other bugs, like the one reported
[comment:ticket:11970:25 here]. Using `TERM=unknown` (or `none`) or
something like that instead would perhaps avoid both.
I don't think that is a good solution, because we need Sage to work with
`TERM` unset. Imagine for example somebody wants to run sage from a cron
script, then `TERM` would not be set. Also, `TERM` is not set when you
run something like
{{{
ssh mysagebox "sage script.sage"
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12263#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
