I'm using Julia on Visual Studio Code. I just found that the error trace is missing if I toggle bash up and down. If no toggle action is done, nothing went wrong, which is not possible for me.
Did anybody ever encounter this before? I'm sure it's a problem with Visual Studio Code because I tried toggle in another bash and the output is trimmed.
Taking this shell as example, a full output is what I need, but when I click 'toggle the panel' (marked red) to editor window and then return to shell, the full output is trimmed, like this. Most part will be lost, sometimes in the middle, sometimes at the beginning.
Related
I have used to watch the red icon in RStudio showing that a script is being executed. It is very intuitive, clear, and handy as a stop button.
Red stop icon in RStudio
How can I get a similar icon in Visual Studio Code using the R extension, indicating the (R)terminal is running some code? Or are the missing + sings a reliable indicator of a running process? However, they do not work as a stop button, obviously.
The settings for the R extension do not give any relevant results with #ext:REditorSupport.r stop or #ext:REditorSupport.r buttonor #ext:REditorSupport.r running.
My terminal in VS Code has since the previous update shown the word ERROR on every single line. I have installed oh-my-posh a little while back to make the terminal more pleasant to look at and give me some basic information.
Does anyone know where to look, to find the source of the error message? Tyvm :)
Update
Noticed something different when running echo $ as suggested by #kamen-minkov
When I booted Ubuntu up again and my VS Code opened from the previous state it was in the ERROR label was gone:
However. When I opened up a new tab it returned:
The only difference I can notice between the two is that there is a little, unfilled, circle/dot on the left side of the newly opened tab and not the one that opened up with VS Code. Is it some sort of debugger marking or something else? Could it be the source of the problem?
Apparently it's the Shell Integration decorations that's causing the hazards..
// settings.json
"terminal.integrated.shellIntegration.enabled": false,
"terminal.integrated.shellIntegration.decorationsEnabled": "never",
disable these settings and oh-my-posh error label will be gone :)
A question from a newbie here: when I run some python code in VSCode, there is always a display of source code in the interactive window. Thus I have to scroll all the way down before I can see the output. That makes the debug quite troublesome.
Please see the screenshot above. The code was displayed in the interactive window despite the editor just at left side over there. Any way to have VSCode, or maybe Jupyter extension, go directly to the output? (in my case starting from the 'Training Dataset shape......')
I am sorry if the question doesn't make sense, I didn't really know how to phrase it properly.
What I am trying to achieve is similar to how it works in the command prompt when running a python file. When I run a python file from the command prompt, the command prompt window will jump to the last outputted line during the running of the program, so what is currently being outputted is always visible. However in my current VS Code set up, the output window will not jump to the last line as it is printed, and I have to scroll through the output window to see what is happening with the program.
I am currently using the latest version of VS Code and using the code-runner extension as well. Please let me know if what I am asking does not really make sense.
Thanks
As far as I understand your question, I would like to answer it.
To Auto-Scroll to the last output, you can just click on the Lock Icon near the Clear Console icon.
Visual Studio Code just updated. This update destroyed the entire looks of the integrated terminal. Spacing between letters seems to be set to some absurd high number.
Does anyone know how I can fix this so the terminal will look as it did before the update?
This is what it currently looks like.