Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Persistent Terminal Layouts and Workspace Templates with Terminal Positions in Editor Area #237007

Open
chrisbensch opened this issue Dec 27, 2024 · 0 comments
Assignees

Comments

@chrisbensch
Copy link

I would love for Visual Studio Code to support saving and restoring terminal layouts, specifically including terminals placed in the editor area. This feature would allow users to create workspace templates with custom layouts, including pinned documents and terminal positions, making it ideal for workflows like penetration testing or other highly customized development processes.

Use Case: As a penetration tester, I often need:

Multiple terminals in the editor area arranged in specific layouts (e.g., side by side).
Persistent workspaces that include pre-configured terminal positions, pinned documents, and editor settings.
Currently, while VS Code supports pinned tabs and tasks, it does not persist terminal layouts in the editor area upon reopening the workspace. Adding this feature would make VS Code an exceptional platform for penetration testing and other specialized workflows that benefit from a consistent and organized workspace.

Proposal:

Extend workspace settings to save terminal positions and layout, including terminals in the editor area.
Allow creating "workspace templates" with predefined layouts, terminals, and settings.
Ensure that pinned terminals and documents can be reopened exactly as saved in the workspace.
Impact: This feature would enhance usability for penetration testers, developers, and anyone working on complex or long-term projects. It would also help position VS Code as an ideal IDE for cybersecurity professionals.

Thank you for considering this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants