New Line issue

[theCrazyCode]

Issue Type: Bug

#print method does not add a newline correctly but somehow still preserves the newline space as if the code was printed on that newline but it is printed on the line where the previous print method was called:

VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

[meganrogge]

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/label info-needed terminal

[theCrazyCode]

json settings file

{
"java.help.firstView": "gettingStarted",
"editor.suggestSelection": "first",
"vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
"files.exclude": {
"/.classpath": true,
"/.project": true,
"/.settings": true,
"/.factorypath": true
},
"workbench.colorTheme": "Material Theme High Contrast",
"files.autoSave": "afterDelay",
"C_Cpp.updateChannel": "Insiders"
}

[meganrogge]

can you provide steps to reproduce the problem IE what you do, what you expect, and the actual result?

[theCrazyCode]

I already put what it was initially supposed to do in my first comment. The screenshot shows what I did and the actual results. So everything you are asking for was already given. Do you not have coding experience when you work at a coding company?

[meganrogge]

@karthiknadig any thoughts here as it's a python debug terminal?

@theCrazyCode escape sequence logging would be helpful

[theCrazyCode]

What do you mean by escape sequence logging?

Pretty much whenever I use the print method it is supposed to put the content inside the print method in a new line not
on the same line.

[karthiknadig]

@theCrazyCode This is not an issue with terminal or VS Code or the extension for that matter. This may not reproduce when you run somewhere else. We have had to deal with this in the past when developing a debugger for python.

This has everything to do with threading and timing. Essentially you need to put sys.stdout.flush() in your code to ensure the stdout is flushed out after each print.

[theCrazyCode]

I don't think that's the problem because when I ran the same code on a cloud python environment I didn't get this issue. And I put the flush command inside at the beginning of my doSomething() function and the issue is still present.

[karthiknadig]

@theCrazyCode Again as I mentioned, this might not repro outside of the debug scenario. You have to add flush after every print, not just the first line.