[Bug]: When stepping, the "Stepped to" message is appended to last line of program output

[steinhh]

Current Behavior

When stepping through code, the message "Stepped to: ..." is appended to last line of program output, making it difficult to read, e.g.,:

Considering: ''% Stepped to: SPMFS_TRAVERSE_DIRECTORY    6
   /mn/sertan/u1/steinhh/spice-svn-wd/idl/spice/spice_make_fiducial_l3qljpg_s
  ymlinks.pro

Here "Considering: ''" is program output, and the stepping message is appended immediately after

Expected Behavior

Stepping messages should occur on a separate line below last program output line

GitHub Repo

No response

Steps to Reproduce

1. Step through a routine printing output

Failure Logs

No response

Operating System

• macOS (Intel x86_64)
• macOS (ARM64)
• Linux
• Windows

IDL Version

9.1.0

Additional Information

No response

[ct6502]

Or maybe we should completely suppress the ".stepover" and "stepped to" messages when we are debugging. I don't know of any other dev apps that actually print messages when debugging. It's fine to print the messages if you actually type ".stepover" at the command line, but if you're using the buttons in VS Code we could probably just suppress them.

[steinhh]

Good point... I'd go with suppressing them both!

The manual .stepover (.so) is not so useful in VSCode anyways, as keyboard focus goes to the code every time, requiring a mouse click to get back and type the next one... pretty useless.

Keyboard focus going to the code is also an irritating "feature" when using the buttons (or F10, for that matter), in general but particularly so if you're manipulating string variables, as the values are not shown in the local variables panel. So you'd like to print them... but that requires a mouse-click every time to get the focus back to the prompt.

Is there a way to prevent the keyboard focus change?