Re^4: Unable to debug due to terminal problem (jump)

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.

Comment on Re^4: Unable to debug due to terminal problem (jump)

Replies are listed 'Best First'.
Re^5: Unable to debug due to terminal problem (work) by tye (Sage) on Oct 27, 2013 at 18:11 UTC
"The environment variable didn't work" would never have translated to "set an environment variable" for me What other "work" can an environment variable do? When you try to use an environment variable, there are really only two ways that the variable itself can fail. Either you couldn't fetch the value, which I've never seen be caused by anything other than it just not being set (in the particular process). Or, you fetch the value and it isn't an appropriate value. So setting the environment variable to an appropriate value does seem an obvious resolution to such a reported failure, IMHO. :) Especially after you look at what value is currently set for it, if any. And I think the names of the variables make what values are appropriate pretty obvious as well, in this context. - tye	[reply]
Re^6: Unable to debug due to terminal problem (work) by marinersk (Priest) on Oct 28, 2013 at 14:08 UTC
I guess I failed to look past syntax and into functionality. What an odd blind spot to have after 35 years in this business LOL. Could it be that age is creeping into my intuition algorithm as a destructive (or at least distractive) agent? Gah. I hope not. I'm too young to be getting bad at this. `:-)`	[reply] [d/l]