Closed SvenAelterman closed 10 months ago
@SvenAelterman I can confirm this is due to having an opening bracket as that breaks the logic due to a collision internally. We use a specific syntax to create the hyperlink and that one's failing because of this. I took the assumption no-one would ever have a single bracket in a folder name, but we all know what assumptions are....
Thank you for investigating.
In my case, the single opening (
is due to my display name in Entra ID (formerly Azure AD) having a text between parenthesis and for some reason, when creating the profile folder, Windows omits the closing )
.
Any way to escape an opening (
, because I can't modify my profile folder name?
@SvenAelterman I'm rewriting the logic, but give me some time as I'm going to enjoy the holidays first. I have a draft ready as I realized the way we do it is rather stupid.
Yes, please enjoy the holidays! Happy New Year 🎉
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
Possibly related to my profile folder name having
(
but no)
, the output of{{ path .Path .Location }}
is off when in my home folder or a subfolder thereof.At first, I thought it was because of the
(
in the folder name, but I created a test foldertemp(1)
and it behaved correctly. A test foldertemp(1
has the same issue.Theme
Custom
What OS are you seeing the problem on?
No response
Which shell are you using?
No response
Log output