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

Feature request: Put open folder name first in window title (better for thumbnails) #18526

Closed
indywill opened this issue Jan 13, 2017 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality

Comments

@indywill
Copy link

  • VSCode Version: 1.8.1
  • OS Version: Win 10 64-bit

Overview:

Having filename first (rather than folder) in window title bar title makes switching between multiple instances more difficult.

Abstract:

Like many developers, I usually have at least 2-3 (often many more) project folders (i.e. code instances) open at the same time, and switch between them. Currently, the window title for each instance is set as follows (at least in Windows version):
[file name] - [folder name] - Visual Studio Code

The problem is that one may be editing a file called 'settings.json' in multiple projects at the same time, making it difficult to quickly discern which tile or thumbnail represents which project when using alt-tab or windows taskbar hover tiles. And if the file name is very long, the folder name may not be visibile at all.

If the folder name were first, it would be much more immediately apparent which tile/thumbnail was which project instance.

Concerns:

While I believe that this would be a simple change programmatically, I must admit I have no idea how this would impact my friends on other platforms since I only use Windows. Perhaps someone familiar with the OSx or Linux versions could share their thoughts on this.

@mjbvz mjbvz added feature-request Request for new features or functionality workbench labels Jan 13, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Jan 13, 2017

@bpasero Since you worked on #3119, can you please take a look at this?

@bpasero
Copy link
Member

bpasero commented Jan 14, 2017

#1723

@bpasero bpasero closed this as completed Jan 14, 2017
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 14, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants