Now I need to nail down if it's Perl or Win which changed.

FYI - on the same system - the same perl run from the powershell command line doe NOT introduce 150 spaces when copied.

So the extra space behaviour seems to be particular to Activestate perl and the windows 'cmd' prompt.

                "From there to here, from here to there, funny things are everywhere." -- Dr. Seuss

Thanks again.

I didn't have time to look into the code, but I seem to remember that different file handles are used for the prompt and for the eval.

Could be that the cmd.exe is messing it up.

Or Activestate patched something.

Good that I asked here, because initially I was blaming emacs, which added more headache to the scenario. ..

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

> So the extra space behaviour seems to be particular to Activestate perl and the windows cmd prompt.

I just tested to run GIT's Perl inside a cmd.exe instead of a GIT-bash and copying worked fine

so it's rather the perl/debugger version conflicting with the cmd.exe

> Git\usr\bin\perl.exe -de0

...
Loading DB routines from perl5db.pl version 1.51
...

  DB<3> say for 1..3
1
2
3

  DB<4>

...
This is perl 5, version 26, subversion 2 (v5.26.2)
[download]

and you're right Powershell doesn't have that problem ... (it's just tooo blue ;-)

  DB<1> say for 1..3
1
2
3

  DB<2>
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}