Every time I launch the vscode, it automatically opens launchd.conf. How do I turn this off.
VSCode always opens the folder on which you were previously working.
Try opening a new folder File > Open Folder > {Some_Folder}, and close VSCode.
Now whenever you open VSCode again, it loads {Some_Folder}.
Related
I have accidently open a 1400GB file on VSCode. now I whenever open the VSC the file opens at the start even after deleting the file it makes the VSC to shut down and close how can i overcome with this solution? I tried reinstalling also but couldn't resolve.
I was trying to open the VSC as normal, but it turned out close down.
All of a sudden Ctrl+Click on a link in the output of the integrated terminal, opens file in a new instance of vscode. This was not happening some time back. How to troubleshoot and fix this?
When I press F5 while developing an extension to launch the Extension Development Host, it automatically opens the desktop directory. I'd like to change this, but I can't find anything relevant in launch.json or settings.
After reinstalling and updating, it just opens the last folder I opened.
When I open my VSCode the default terminal that gets opened is PowerShell. I wants the default one that gets opened to be CMD. How can I change it?
I have configured the Terminal: Select Default Profile to be CMD and its also made sure as seen in the below pic.
I restarted the VSCode several times, still on opening VS Code the terminal that gets opened is PowerShell. Should I make any changes to settings.json?
Using Visual Studio Code (latest version as well as prior versions), when using the command line to launch I am seeing some odd behavior. Trying to determine if I am missing something, or if this is a bug.
Here is the scenario.
Action 1: I have a workspace open with a couple of files open for editing. If I close VSCODE, and then just open it again the state is restored, I am in the workspace and the files are open for editing. Great.
Action 2: I have a workspace open with a couple of files open for editing. If I then from a command line do "vscode testfile.txt" then the new file gets opened in VSCODE and joins the other opened file. Great.
Action 3: I have a workspace open with a couple of files open for editing. I close VSCODE. I then from a command line do "vscode testfile.txt". VSCODE starts up, but only the new file gets opened in VSCODE. The workspace I had opened is not any more, and the files I had opened are no longer opened. Not so great.
I have tried adding the -r option on the command line but that didn't change anything.
This feels like a bug, but if not help me understand how I get the desired result, which is when VSCODE is not running, and I try to edit a file from the command line, I want VSCODE to restore to the state it was in when last closed, and then add that new file to the mix. Just like if it was already running.