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.
Related
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}.
I am trying to figure out if its possible to have vscode reopen my remotely saved workspace on open of the program automatically.
Additional info:
I have the settings for a normal reopen on (restoreWindow).
I see the workspace on my Open > Recents, but I want to automate this part
Interestingly after a couple times opening and closing (didn't really pay attention to it, after two hours I noticed), it opens the workspace on its own. I was reopening it manually from Recents in the meantime.
It would be great to know where is this info stored in vscode to debug it manually.
I open a file on a BeagleBone Black running debian 8.4 with VScode via SFTP with winSCP. By right clicking > edit > code.
When the file opens, VScode also opens three new files named visual, studio, and code (image attached). I did not create these files myself. Opening files from other sources does not cause this.
I have tried closing the files individually. Connecting and reconnecting. Opening and closing VScode. In every possible order and configuration. They return every time when opening another file with the same method.
This is how I have set up VScode as an editor in WinSCP.
This is extremely odd, and only trivial, yet highly annoying.
What's causing this? How do I stop it?
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.
I've never seen this before so thought I'd ask here. My vscode isn't showing the latest changes in a file. When I open said file with vim, the file is up-to-date as expected. If I open that same file in vscode, it shows something else.
I've tried restarting vscode, using the 'Clear Editor History' command to clear the editor cache... I've restarted my machine. Nothing seems to work. Any thoughts?