The absence of a built-in feature to open tabs in new windows has been a persistent concern among Visual Studio Code users. Several workarounds have been proposed, including:
- Duplicating the workspace
- Opening the active file in a new window
- Dragging files to a separate instance
However, these workarounds are not without limitations. For example, multiple copies of the same file may be open, and changes made in one instance may not be reflected in others. Additionally, opening a new window can lead to complications with working directories and linters.
Despite being a highly requested feature, Visual Studio Code does not currently support floating windows. As a result, users have resorted to using keyboard shortcuts, command input, or third-party tools like PowerToys.
The issue of opening tabs in new windows remains unresolved and is actively being discussed on the GitHub platform. This article aims to explore the methods, challenges, and alternative solutions related to opening tabs in new windows in Visual Studio Code.
How to Open Tabs
Opening tabs in new windows has been a highly requested feature for years. Visual Studio Code currently provides workarounds such as:
- Duplicating workspaces
- Opening the active file in a new window
- Dragging tabs to separate instances
However, these workarounds have their limitations. They do not sync breakpoints or local variables, and opening a new window does not load dependencies or functions from libraries. Additionally, opening the same folder in two instances is not allowed.
Despite the availability of these workarounds, the issue of opening tabs in new windows remains open and locked on GitHub, indicating that users are still seeking a more efficient solution.
Common Issues
Common issues with opening tabs in new windows include:
- Lack of persistence of changes made in one instance to other instances
- Difficulties in loading dependencies or functions from libraries
- Inability to sync breakpoints or local variables between windows
When opening a new window, the changes made in one instance do not carry over to other instances, making it inconvenient to work with multiple copies of the same file.
Additionally, opening a new window does not load dependencies or functions from libraries, which can hinder the development process.
Another drawback is the inability to sync breakpoints or local variables between windows, making debugging more challenging.
These issues have been raised by users for years, and although workarounds exist, such as duplicating workspaces or dragging tabs, a built-in solution to open tabs in new windows is still awaited.
Workarounds and Shortcuts
Various workarounds and shortcuts have been suggested to address the challenges of opening tabs in new windows in Visual Studio Code.
One workaround is to duplicate the workspace in a new window, allowing for multiple instances of the same file to be open.
Another option is to open the active file in a new window, which can be done by pressing Command + K followed by O.
Additionally, dragging a tab to an empty space in the editor will open it in a separate blank instance.
Workspaces can also be used to open the same directory side by side.
However, it is important to note that opening a new window may cause issues with working directories and linters, and it does not load dependencies or functions from libraries.
These workarounds and shortcuts provide alternatives for users who desire the ability to open tabs in new windows.
