[Octave-bug-tracker] [bug #45509] communications-1.2.1 fails during package install in octave-4.0.0

[anonymous]

Follow-up Comment #24, bug #45509 (project octave):

And here's this as well:

http://stackoverflow.com/questions/15760712/python-readline-module-prints-escape-character-during-import


Setting my TERM environment variable to vt100 prior to starting octave allowed
the communications package to compile as if I logged in via ssh.  

Honestly I don't see how this is a useful solution though since the TERM
variable is set to xterm when I ssh too, so it's not *quite* the problem; it's
just the difference of being a tty or not.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45509>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/