in reply to Re^4: Threads Printing Issue - Output Mangled / Term Crashing
in thread Threads Printing Issue - Output Mangled / Term Crashing

I don't see any error on your code so I blame the unknown! :-)

Now seriously, yes, the TTY handling code in OpenSSH is quite hairy and bugs there are not so uncommon as one would like.

  • Comment on Re^5: Threads Printing Issue - Output Mangled / Term Crashing

Replies are listed 'Best First'.
Re^6: Threads Printing Issue - Output Mangled / Term Crashing
by bigbot (Beadle) on Apr 14, 2014 at 23:10 UTC
    OK great suggestion I should have thought of this sooner. It was the only option I changed in the SSH line and that was most likely causing the issue. I just find it weird that simply putting that output in a variable can mess up your local prompt.
[reply]

      It is not "putting something in a variable" that changed your local prompt, i.e. not something that ssh sent to its output, but something that ssh did to its (and per the -t Option: your) terminal

      ... just like changing the time (e.g. via `date -s ...`) affects the whole System, regardless of whether you assign that command's output to a variable or print it directly (or discard it completely)

      In programming this is called a side effect, although it is often the main reason for doing it :-)

[reply]
[d/l]
[select]
        Yeah that's true. I was looking at it the wrong way. I think I have a pretty good idea of what the issue is with this new information, thanks.
[reply]

In Section Seekers of Perl Wisdom