You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue occur when all extensions are disabled?: Yes/No
VS Code Version: 1.90.1, maybe since we have multi-root workspace system
OS Version: Windows 10
Steps to Reproduce:
Open some folder in vscode
Add some more folders into workspace and it would become workspace
Open folder that already opened in workspace with cli code <opened folder>
Result behaviour is, it will just open a new window with a folder that already opened in another window workspace
With -r option it then trying to close the last active window and reopen into only that folder
With -a it then try to create workspace if that folder is not yet opened
Drop the folder and only open the file with -g then it might open a last active window that not a window that actually contain the file
All of these are not ideal
I wish that if there is any workspace already contain that folder it should just make that window become active and use it. But if there is none then it should open new window normally. This should be default behaviour of vscode without any flag
If it can't be default behaviour then I would like to propose a new flag, such as --reused-if-exist/-re
Also sometimes we would like to open folder to existing workspace, but specifically to workspace that already contain folder we known. And so I would like to also propose that there could be a flag --add-to <mainfolder> which will check that, if the mainfolder already opened in any window, it would use that window to create workspace
Or maybe let it that, when we open code with list of folder into workspace, if the first folder in the list already opened, vscode will use that folder as the main, choose opened window as a base, and open workspace in that window
Is this behaviour possible?
The text was updated successfully, but these errors were encountered:
The code here was tested only if the workspace itself has the same root as the folder it try to opened but not ask for the opened folder inside workspace unlike findWindowOnFile above
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
code <opened folder>
Result behaviour is, it will just open a new window with a folder that already opened in another window workspace
With
-r
option it then trying to close the last active window and reopen into only that folderWith
-a
it then try to create workspace if that folder is not yet openedDrop the folder and only open the file with
-g
then it might open a last active window that not a window that actually contain the fileAll of these are not ideal
I wish that if there is any workspace already contain that folder it should just make that window become active and use it. But if there is none then it should open new window normally. This should be default behaviour of vscode without any flag
If it can't be default behaviour then I would like to propose a new flag, such as
--reused-if-exist
/-re
Also sometimes we would like to open folder to existing workspace, but specifically to workspace that already contain folder we known. And so I would like to also propose that there could be a flag
--add-to <mainfolder>
which will check that, if the mainfolder already opened in any window, it would use that window to create workspaceOr maybe let it that, when we open
code
with list of folder into workspace, if the first folder in the list already opened, vscode will use that folder as the main, choose opened window as a base, and open workspace in that windowIs this behaviour possible?
The text was updated successfully, but these errors were encountered: