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
I have a win32 store app (desktop-bridge) converted and it works fine.
I want to create a desktop shortcut for this Store App that
uses AUMID to start the app (solved below)
and also passes an argument to it (not solved)
Here are the things I have tried:
I know how to start the app from command line using its AUMID.
explorer shell:appsfolder\[aumid]
I see that I can even use this as a target in a desktop shortcut and it works.
Now, I also want to pass arguments to the app which I can't do with the explorer command above.
But if I use start, it works:
start shell:appsfolder\[aumid] "an-argument"
But I can not put the above start command as target in a desktop shortcut. So how do I create a desktop shortcut that is able to start the store app above with an argument?
Another way to look at this question is, how to create a desktop shortcut with the start command?
Update: Got an answer from another question and the following works in the shortcut except that there is a blink when the command line window comes and goes.
cmd /c start shell:appsfolder\[aumid] "an-argument"
I've created a simple game using Phaser on vscode.
I read that i need to run it locally in order to run it on chrome and i can't manage to do so using vscode's F5.
when im on "index.html" and pressing F5 it pops out an alert box that says "cannot find progrem to debug".
pressing F5 while im on any other file causes a error in the debugger "window is not defined"(when im on phanser.js)/"Phaser is not defined"(when im on any other file)
how can i start this program correctlly ? sorry for the basic question .
http-server works just fine. But if you want to debug the game easily. You might want to follow the steps in this post: https://divillysausages.com/2015/06/09/using-phaser-with-visual-studio-code/
It is an instruction for setting up Typescript phaser development in vscode, but the steps that teach you how to set up node server also applies to a javascript usage case. If you want to make it easy to debug(pause code executing while game running, etc.) Try to set it up in that way.
Had to install http-server from npm and run it in terminal.
tried it before, but accidently installed it not globaly.
now it works. thanks!
My VS code terminal was working fine, until one day when I tried to work on a project, that was still open in VS code, my terminal didn't allow me to type any commands. I couldn't type anything. This is the screen that I get.
Okay, for those of you struggling with the same problem, I've managed to solve it by clicking on the drop-down menu that says powershell and changing it to cmd.
this happened to me and simply
close vs code
right click on it
run as administrator
open the terminal and it will work
this problem happened when I changed the default path of CMD
For me, I tried using Powershell/CMD/Bash and I was having errors/blank terminal. I found typing echo hello and pressing CTRL + C made it appear. So in fact, everything was working, my terminal was just blank/glitched out, but was really accepting input.
I had a similar issue when running ionic serve command which runs the development server on the localhost. I paid attention after executing the command above, and it said:
Use Ctrl+C to quit this process
Pressing Ctrl+C then displays:
Terminate batch job (Y/N)?
Type Y or y
then the command prompt is shown again!
Here is a sample terminal window - trimmed for brevity:
For who has this problem using React. This happens when you start a live version using npm start. The terminal that handles the live version of the app cannot be used for anything else.
So to continue using the terminal you need to open a new terminal to use in parallel. To do so just click on the plus icon in the top right corner of the terminal panel then choose the "Power Shell" option. This will open a new terminal without restarting visual studio.
In Mac, when working with Python, this helped me: instead of clicking on the "Run Code" option, click on "Run Python file", in the right corner.
For Ubuntu users this is solved by this solution:
File -> Preferences -> Setting -> Features -> Terminal -> Inherit Env
I found two vscode on my desktop, I opened the other one and it worked. Looks like I updated it but the older one didn't disappear.
If typing Ctrl+C can help to get out of this frozen state, that will be easier to do with VSCode 1.64 (Jan. 2022)
The terminal can type the answer for you.
Terminal -- Auto-reply
The terminal is now able to automatically reply when a specific sequences of characters is received.
A good example of where this is useful, which is also the only default case, is the Windows batch script message Terminate batch job (Y/N)? after hitting Ctrl+C when running a batch script.
This typically just ends up causing problems for the user.
The terminal will now automatically reply with Y and enter (\r) which makes Ctrl+C in Windows feel much better.
Pressing Ctrl+C will immediately reply to the question and return to the prompt:
Theme: Sapphire
The feature was made generically so you can setup custom replies for other thing, just be careful when doing this as you are sending text to the process automatically.
For example you could use it to automatically update Oh My Zsh when prompted:
"terminal.integrated.autoReplies": {
"[Oh My Zsh] Would you like to check for updates? [Y/n]": "Y\r"
}
If you use Clink and enable their similar feature, you can disable it in Clink or in VS Code by setting the reply to null to avoid the two features conflicting with each other:
"terminal.integrated.autoReplies": {
"Terminate batch job (Y/N)": null
}
Go to terminal, preferences, settings.
Check "run code in terminal"
Restart VS.
I changed from bash to powershell in terminal first but the command prompt still not shown.
Then I navigate to File -> Perferences -> Settings and it starts working (command prompt shown)
This seems to just be a display problem. It happened to me when I changed my display settings for desktop icon and app scaling settings.
I managed to fix the problem by simply restarting my computer and re-opening VS code
I had the same problem ... In my case just run vs-code as administrator and works
How do you run and debug an interactive Node.js app (one that prompts the user to enter STDIN on the console) in VS Code using a simple launch (F5). I have so far been running the app using node --inspect-brk . and then attaching VS Code. This works fine, but I'm just wondering if there's a faster way. If I look at the DEBUG CONSOLE pane, I can see the STDOUT, but I can't add input there.
Randy's comment was my answer with a link here. Thanks, Randy.
The solution is to configure the console value in your launch.json file. I added "console": "integratedTerminal" and now when I hit F5 I can jump to the integrated terminal (CTRL+<backtick>) and interact with my app.