Silence the startup command printout in Integrated Terminal

[mymikemiller]

When I run a Dart app in the Integrated Terminal, it prints out a very verbose startup command, e.g.:

cd /Users/mikem/myproject; /usr/local/Cellar/dart/2.8.2/libexec/bin/dart --enable-vm-service=0 --pause_isolates_on_start=true --write-service-info=file:///var/folders/2n/vn59_vz152vg107rrs53ympc0000gn/T/dart-vm-service-ee74.json -DSILENT_OBSERVATORY=true --enable-asserts bin/main.dart

This happens for Javascript too:

mikem@MBP node_sample % /usr/local/bin/node --inspect-brk=6018 scripts/simple.js Debugger listening on ws://127.0.0.1:6018/453abe68-1da3-4862-8ba4-71d8e3dfd8d6 For help, see: https://nodejs.org/en/docs/inspector Debugger attached.

These printouts pollute the scrollback and aren't very useful imho. Could we get an option to silence this output, so the first thing I see in the Integrated Terminal is one of the print statements actually in my code?

Note that this doesn't happen when using the Debug Console. There, I only see this printout (which also would be nice to silence, but at least it's less verbose):

Connecting to VM Service at ws://127.0.0.1:58210/4yciVJ1NsWE=/w

[weinand]

@Tyriar is there a good way to executed a command in the integrated terminal but turning off echoing?

[weinand]

@mymikemiller if the debug console works for you, why are you not using it instead of the integrated terminal?

[ArturoDent]

You can turn off echoing commands in bash for example.

set +x

in your C:\Program Files\Git\etc\bash.bashrc

There is also a verbose +/-y switch in some shells. See https://stackoverflow.com/questions/2853803/how-to-echo-shell-commands-as-they-are-executed

I don't know if either of those would affect the startup commands that you are seeing?

[mymikemiller]

@weinand The debug console doesn't accept interactive input, and also it doesn't allow me to position the cursor absolutely, which is required for a library I'm using to print out nice progress bars.

[mymikemiller]

@ArturoDent I don't think this is a bash thing (I use zsh, but same thing). When I run dart bin/main.dart, my app runs without echoing any command. So this seems to be a VSCode issue.

[mymikemiller]

Btw, I get the same output with bash as my default terminal as I do with zsh:

bash-3.2$ cd /Users/mikem/myproject ; /usr/local/Cellar/dart/2.8.2/libexec/bin/dart --enable-vm-service=0 --pause_isolates_on_start=true --write-service-info=file:///var/folders/2n/vn59_vz152vg107rrs53ympc0000gn/T/dart-vm-service-f583.json -DSILENT_OBSERVATORY=true --enable-asserts bin/main.dart

[mymikemiller]

@ArturoDent Switching to Bash and adding set +x to the top of my .bashrc does not get rid of the printout. It does stop my bashrc from printing out any of its commands, which are printed if changed to set -x.

[weinand]

@mymikemiller are you saying that when you are typing dart bin/main.dart in zsh, you are not seeing what you are typing?

[mymikemiller]

@weinand correct.

In a normal terminal:

In VSCode's integrated terminal when debugging:

[DanTup]

FWIW, when debugging here - the app is being spawned with the DAP's RunInTerminalRequest request, it's not being run explicitly by manually the command in the terminal.

[weinand]

@mymikemiller your zsh echos the command you are typing. The short dart bin/main.dart command in your first screen shot corresponds to the long command in your second screen shot.

The only difference is: VS Code creates a much longer command from data received from the dart extension because it has to make sure that the command is run in the correct directory and the environment variables are correctly set up. This result in a longer command.

VS Code does not "print out" anything here. It is your zsh that echoes the command received from VS Code.

[mymikemiller]

@weinand It's not my zsh printing it, though. In the first screenshot, the text is there from me typing in the command and pressing enter. It doesn't print out the command again.

[mymikemiller]

The issue also occurs when bash is my default shell:

[weinand]

@mymikemiller in the second screenshot the text is there from VS Code typing in the command and pressing enter.

So the behavior is identically. You typing or VS Code typing makes no difference.
You don't see the text twice in the second screenshot, right?

The only difference is that VS Code has more to type.

In your initial comment on this issue you are complaining about this "printout":

cd /Users/mikem/myproject; /usr/local/Cellar/dart/2.8.2/libexec/bin/dart --enable-vm-service=0 --pause_isolates_on_start=true --write-service-info=file:///var/folders/2n/vn59_vz152vg107rrs53ympc0000gn/T/dart-vm-service-ee74.json -DSILENT_OBSERVATORY=true --enable-asserts bin/main.dart

But if you read this "printout" carefully you will find that this is not "printout" but it is the actual command that VS Code is "typing" into VS Code's Integrated Terminal. If you would type the same manually it would look identically.

[mymikemiller]

@weinand This is a feature request, though, not an issue. (I think I filed it as such)

From the initial post: "Could we get an option to silence this output, so the first thing I see in the Integrated Terminal is one of the print statements actually in my code?"

I think that's a valid request for a feature.

[weinand]

Sorry, but you called it issue:

When I run dart bin/main.dart, my app runs without echoing any command. So this seems to be a VSCode issue.

I tried to explain that this is not a VS Code issue because VS Code is not "printing" out anything.

VS Code is just "typing" a long command that starts with "cd /Users/....; bin/main.dart" into the Integrated Terminal and the shell in that terminal echos the command in the same way it is echoing when you type manually.

I will open this as a feature request.

[DanTup]

In current Insiders build, this is really noisy for NodeJS now:

[testforstephen]

+1

We also received feedback from multiple users complaining that the startup command printed into the integrated terminal is too long when running Java application in terminal.

[testforstephen]

Currently, if the start command is long, it is wrapped into multiple lines by the terminal. Users cannot quickly find the real starting point of the program output. This is the main pain point.

If the integrate terminal allows disabling the line wrapping, that will mitigate this issue too.

I found there is an existing feature request to support disabling line wrapping in integrated terminal. #74501