Re: Unable to debug due to terminal problem (read)

The error message you quoted tells you one simple way to work around it:

set LINES=40
set COLUMNS=80
[download]

Comment on Re: Unable to debug due to terminal problem (read) Download Code

Replies are listed 'Best First'.
Re^2: Unable to debug due to terminal problem (read) by marinersk (Priest) on Oct 24, 2013 at 16:42 UTC
I always knew tye was more brilliant than me, but this one really makes me feel stupid. Where in his quoted error message do you see that solution made evident? I must be completely blind. As always, the question is most sincere. I really don t see how you came to that conclusion.	[reply]
Re^3: Unable to debug due to terminal problem (jump) by tye (Sage) on Oct 24, 2013 at 18:26 UTC
"Unable to get Terminal Size" then "The COLUMNS and LINES environment variables didn't work". The "set" lines I showed are how you set environment variables in Windows. Is there any other steps from the messages to the solution that still aren't clear to you? - tye	[reply]
Re^4: Unable to debug due to terminal problem (jump) by marinersk (Priest) on Oct 27, 2013 at 13:34 UTC
I am going to presume this is due to my lack of familiarity with the module itself. "The environment variable didn't work" would never have translated to "set an environment variable" for me, absent some other reason to draw that line. Thanks for the note.	[reply]
Re^5: Unable to debug due to terminal problem (work) by tye (Sage) on Oct 27, 2013 at 18:11 UTC
Re^6: Unable to debug due to terminal problem (work) by marinersk (Priest) on Oct 28, 2013 at 14:08 UTC