Why is the VS Code terminal adding cr-lf characters to the initial prompt? - visual-studio-code

I just installed Win 10 1809 on my Dell PC, and it seems to run okay. But now there is a problem with the terminal. After the 1809 install, the first thing I did was start up VS Code. I wanted to run yarn start for my React project, but I had to type it way down in the terminal window, while the prompt was at the top. The screen clip below shows the terminal display after I enter "yarn start". The typed input shows up way down from the initial prompt, and the blank area is a long string of "0D0A" characters. Can this be fixed? I did uninstall and reinstall VSCode, but no fix.
In the screen grab shown above, you can see the space that is filled with "0D0A" characters.

Related

VSCode Python terminal output disappears

The terminal output just disappears. A few days ago VSCode started to show this weird behaivor when trying to run a Python code. However, running the code directly from the terminal seems to be okay. Does someone know why this is happening? As far as I know both output should be the same.
I have been using a VSCode for a while and am familiar with VSCode settings and set all to default except for the Default Profile: Command Prompt.
Image 1: Running with the play button
Image 2: Running with the terminal command

VSCode hangs when trying to run a Jupyter notebook?

I am trying to run a Jupyter notebook in VSCode. I have successfully run notebooks in the past, but something has happened to make VSCode "hang" when I try running. When I hit run, the terminal shows the file location and the location of python.exe as expected (shown in the first image, with some personal information redacted), but nothing ever happens. The code never completes and the cells never output. I get a small "pending" icon of a clock and an arrow (shown in the second image) to tell me a cell is running, but even the most basic "Hello, world" never completes or gives an error. I have no trouble running regular python files, and if I export an ipynb to py I can run it, but I cannot run the ipynb itself. Trying to restart the Jupyter kernel also seems to hang, never completing and never crashing or erroring. The only clue I really have is that when I hit F5 to run, there's no python version showing in the bottom left corner, the way there is when I run py files (third image is while trying to run ipynb and fourth image is while successfully running py).
I have tried uninstalling and reinstalling the Jupyter extension from VSCode and restarting VSCode between every step. I have tried swapping between python.exe and conda.exe in the terminal settings python.condapath. I have checked that the windows terminal is cmd. I've tried creating new notebooks in VSCode that only have print("Hello, world"). I have tried the command "Select interpreter to start Jupyter server" and selected the correct version of Python, but nothing has changed any time I've tried to run.
I am using Anaconda version 4.10.3, VSCode 1.61.2, IPython version 7.9.0, and Jupyter notebook version 6.4.3.

How to get Clean Terminal in VSC

I want to have a clean Terminal in VSC, but every time I run my code there is some useless stuff I would like to remove, for example my Microsoft Version and the path to my files.
Is there any way to remove them from my Terminal?
On all my other PC's I don't have this Problem, only on this PC. I already tried to change the console argument in my Launch.json but if I change it to InternalConsole it dosen't run the code anymore. Also it would show my results in the debugger and I would like to use the Terminal.
You can clear your Terminal after each run, by typing clear in Terminal. To have it done automatically, check 'Clear Before Reusing', or 'Clear Previous Output' (if you're using Code Runner) in Settings. To get there, press Ctrl + , on Win or Command + , on Mac and type 'clear' in the search box.
Sending the output to the Debug console looks cleaner, but it doesn't allow user input. Other than that, I don't think there's a way to not have the path of your file displayed as the file executes.

VSCode on Linux Mint, integrated terminal not able to type anything

Hi I'm running Linux Mint 19 and I have just installed vscode using the snapd package manager. I've not used vscode on linux before as my usual editor is emacs. However, on a fresh new install of vscode, the integrated terminal does not work, there is just a non blinking cursor in the top left of the screen, but no prompt and no keyboard strokes are registering. This appears to be a common problem as there are a lot of posts about it if googled, but they are all for Windows versions and none of the solutions that I'm able to try do anything. I've tried to open a new terminal window, but the same thing happens I just get two terminal windows that I now cannot use. I've also tried checking the box that says Code-runner: Run In Terminal, but that does nothing either. What can I do to get this to work please, I looks to me like it is just not connected to either a bash or Zsh(which I normally use). Any help on this would be appreciated.
Instead of starting vscode with its default shell script (usually located on /usr/share/code/bin/code), the integrated terminal only works for me when starting it directly from the compiled binary (typically found on /usr/share/code/code, which is the same as the launcher created by the installer:
/usr/share/code/code --no-sandbox --unity-launch %F
While I searched for a solution in the past I've also noticed that lots of folks solved similar problems just by adding --disable-gpu flag, so might be worth checking out as well.

Bash terminal not allowing typing

I am attempting to use the integrated terminal within VS Code on a Windows 10 box with the bash terminal. I have been using this same setup since March, but now it all of a sudden will not allow me to type anything in the terminal. When I start VS Code the terminal opens, but with the screen scrolled all the way down, if I scroll up I can see the command prompt. If I try to type it just scrolls back to the bottom again and doesn't type the characters. Has anyone seen this before?
Visual Studio Code 1.47.1
Git Version 2.27.0-64-bit
I have been using Git Bash while this isn't working without issue.