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

Re-launch previously opened windows on their previous virtual desktops (KDE/Kubuntu) #57530

Closed
davidleejy opened this issue Aug 29, 2018 · 2 comments
Assignees
Labels
electron Issues and items related to Electron *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@davidleejy
Copy link

I don't mind chipping in to implement this feature. Advise welcomed.

Background:

Currently on Kubuntu (== Ubuntu with a KDE GUI). KDE has "activities" and "virtual desktops" - a bit similar to Windows. Relaunched vscode windows (say, after rebooting machine) do not remember which activity or virtual desktop they were on earlier - all windows launch in the same virtual desktop .

Benefits of this feature:

Makes it more natural for programmers to work on several code projects by saving users the effort of re-locating windows to their previous desktop after shutdowns/reboots.

I don't mind helping to implement this feature:

I'm new to the vscode code-base. Would be nice if vscode maintainers/contributers could advise roughly where to look. My (uninformed) guess is that at least 2 changes will have to be made:

  • Similar to how opened tabs are remembered, opened windows' virtual desktops can be remembered too. Implement recording of this extra information.

  • Launching vscode needs additional logic to re-locate windows to their respective virtual desktops. Check if target desktop exists.


Similar feature request to #35240 but this is for KDE.

@vscodebot
Copy link

vscodebot bot commented Aug 29, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@bpasero bpasero added upstream Issue identified as 'upstream' component related (exists outside of VS Code) electron Issues and items related to Electron labels Aug 30, 2018
@bpasero bpasero added the *out-of-scope Posted issue is not in scope of VS Code label Oct 9, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 9, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
electron Issues and items related to Electron *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants