in reply to Problems starting the debugger

Thanks for the update! Just for reference, here's one thread with the same problem and solution:

And a couple of threads with similar advice to set TERM=dumb:

Replies are listed 'Best First'.
Re^2: Problems starting the debugger
by morelenmir (Beadle) on May 20, 2018 at 15:14 UTC

    Many thanks indeed haukex!!! I will check those threads out next.

    It was so weird I couldn't find the same list of posts when I searched at first. I think it may have been a stale browser cache or something. Either that or I had transcribed the error message wrongly but my eyes glazed over the inaccuracy.

    In regards the 'TERM' environment variable; is that a new thing? I have dabbled with the debugger a very little in the past and it never came up with that error before. I am pretty sure I didn't have 'dumb' set on those occasions.

    Anyway--all's well that ends better!!!

    "Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.
[reply]
      In regards the 'TERM' environment variable; is that a new thing?

      The variable itself is AFAIK not new, I think it's been around on *NIX systems for a long time, but not on Windows. But since many *NIX tools have been ported to Windows nowadays, they often still expect the common *NIX environment variables to be around.

      I am pretty sure I didn't have 'dumb' set on those occasions.

      I don't know, either the issue just didn't exist before, or it might have been set for you by a batch file like Strawberry Perl's portableshell.bat - in this node, Athanasius mentioned that Strawberry Perl 5.18.2 did set TERM=dumb, while 5.20.0 did set TERM=.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom