Script is being echoed to the terminal

[ArchieCall]

On vsix 0.15.27 the whole script is being echoed to the terminal before any execution starts. If the script is long (say 2000 lines) there is a sizeable time lag, and the terminal is cluttered up with needless lines that are just repeating what is already in the editor.

[davidanthoff]

So my current idea is that when one executes a whole file, that we just echo an include("bla bla")? Would that make sense?

[ZenanH]

I also ran into the problem above🙋, if terminal can just return “include(...)” or show nothing as before, both are fine for me.

[ArchieCall]

That is how I work around the issue on the latest version. It must have worked that way with the version that was only 10 days old as it does not echo to the terminal.

…

On Thu, Apr 30, 2020 at 5:15 AM David Anthoff ***@***.***> wrote: So my current idea is that when one executes a whole file, that we just echo an include("bla bla")? Would that make sense? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1153 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHMQWRNBQ42HPWKJKIT3DLRPE6TNANCNFSM4MT665OQ> .

[ArchieCall]

This issue is shown as being closed and I do not think it has been corrected! Also if it opened back up, could the Juno Parity label be applied... Thanks.

[davidanthoff]

Issue is still open :)

I'm not going to apply the Juno label, mostly because this issue is quite trivial to fix and we want to keep the Juno label for big features where we are missing parity, i.e. the things where the two teams need to have some extensive design discussions.

[pfitzseb]

Fiexd now.