-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
[BUG] - The status bar does not show the name of the currently loaded project when using a relative path. #650
Comments
Hi @jaronfort , I'm not sure this is a Windows related issue, but I couldn't reproduce the error on my MacOS. The Btw, does the project path is properly displayed (expanded) when you hover the project in the Project Manager - Favorites view? It should display
Hope this helps |
Sorry, I made a mistake. It is actually working fine for me on macOS. I
tried replacing the paths to use the "/" delimiter instead of "\" (which is
escaped in the string literal as "\\") and still no luck.
[image: screenshot.1.jpg]
I also confirmed that I can see the project path, workspace icon, and
project name when I hover over it in the favorites view.
Btw. Thanks for creating this extension. This has definitely improved my
workflow.
…On Fri, Sep 23, 2022 at 3:54 PM Alessandro Fragnani < ***@***.***> wrote:
Hi @jaronfort <https://github.com/jaronfort> ,
I'm not sure this is a Windows related issue, but I couldn't reproduce the
error on my MacOS.
The ~ shortcut is supported on project paths and it seems to be properly
*expanded* on project detection of the Status Bar, so it is really weird
it is not working in your case.
Btw, does the project path is properly displayed (expanded) when you hover
the project in the Project Manager - Favorites view? It should display
Project Name
c:/Users/Me.... (expanded path)
Icon Workspace
Hope this helps
—
Reply to this email directly, view it on GitHub
<#650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADB3AHUNZFWMV46IUSQ4VATV7YYI7ANCNFSM6AAAAAAQUKNS2Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Just to let you know, I could reproduce the error on a Windows machine, and neither So, it is definitely something OS specific. Thanks for reporting |
No problem.
…On Mon, Sep 26, 2022 at 8:11 AM Alessandro Fragnani < ***@***.***> wrote:
Just to let you know, I could reproduce the error on a Windows machine,
and neither $home keyword is working.
So, it is definitely something OS specific.
Thanks for reporting
—
Reply to this email directly, view it on GitHub
<#650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADB3AHWKAG5E4V7SCMKSV5TWAG4ITANCNFSM6AAAAAAQUKNS2Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, |
Environment/version
Steps to reproduce
projects.json
file and change the workspace path of the new project to use~/Documents/MyProjects/my-project.vscode-workspace
(instead ofc://Users/Me/Documents/MyProjects/my-project.vscode-workspace
.The text was updated successfully, but these errors were encountered: