On Windows, when I open a folder from the terminal in VSCode with the "code ." command, it opens VSCode correctly but the terminal window becomes a slave, running all console commands from the app without returning command to me. If I close the terminal, VSCode also closes, it seems that the application thread is being run as child of the terminal process that gets killed with its parent. The same does not happen with "xp . ", my shortcut for the file explorer.
My question is how to make VSCode open as its own process letting the terminal be free.
