-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Display the full workspace path in UI #3119
Comments
+1 |
Perhaps installing the Active File In StatusBar extension would answer the problem. |
+1 |
@bpasero will that be released next month? |
@kentor, yes, November release. |
The only bummer here is that if you go full screen, which I do often with a split pane view in macOS (VSCode on the left, Chrome browser on the right), then you can't see the title bar of the application. |
@martynchamberlin I think that is the point of going fullscreen in the first place. What is useful is to disable tabs and just benefit from the fact that the space you get from disabling tabs is used to show the path of the file: (though arguably this does not have a setting to show the full path, only on hover it gets revealed) |
Oh cool, didn't know about this. Thanks! Trying it now. |
@bpasero |
@bsienn
from http://code.visualstudio.com/updates/v1_10#_configurable-window-title |
Ahh, I didn't read the whole change log. My bad. Thanks for super quick response. |
Thanks @bpasero! |
add this line "window.title": "${activeEditorLong}", works for me |
I have two workspaces:
c:\docs\dev\version1\js
and
c:\docs\dev\version2\js
If I open one VisualCode instance with the workspace
c:\docs\dev\version1\js
and another one withc:\docs\dev\version2\js
there no easy way to know which window points to which workspace.The only information that is displayed in the UI is the last folder of the workspace's path which is in both cases
js
so it's not really helpful.It would be great if there was an option to show the full path to the workspace instead of the last folder in the UI.
The text was updated successfully, but these errors were encountered: