#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:8 wjp]:
> Out of curiosity, do you really get an unset TERM in cron jobs and non-
interactive ssh sessions? On all of the systems I've tried, it's always
'dumb'.
Are you sure there is an '''environment variable''' "TERM" in the cases
you mention? It seems to me that bash sets a non-exported variable
TERM=dumb if there is no environment variable TERM. You can see this with
"declare -p TERM". In a normal shell, I get for example
{{{
$ declare -p TERM
declare -x TERM="xterm"
}}}
(the -x means exported)
With a non-interactive ssh session:
{{{
$ ssh sage.math.washington.edu "declare -p TERM"
declare -- TERM="dumb"
}}}
(no -x, so not exported, i.e. not an environment variable)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12263#comment:9>
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.
