Closed KohlJary closed 7 months ago
@KohlJary Thanks for bringing this to my attention, I shall look into this. Slashes in git branch names is a common practice and should definitely be supported.
To be precise, the issue was exhibited on Windows 10 Enterprise, I suspect due to backslashes being escaped but not forward slashes, found a similar issue in another plugin where that was the root cause. I can take a look myself sometime soon here.
Pretty sure the call to prosession#GetCurrBranch here needs to be wrapped in a fnamemodify() call, let me get this forked and try it and see how it works.
Nevermind I was way off base, issue is related to Windows handling specifically and how the git branch command is called/the default git branch command. Gonna take some time after work today to tighten it up then I'll have a PR for you.
@KohlJary Thanks a lot!
@KohlJary closing this issue for now. Let me know if you need any help for the PR to fix this ?
I've been using the version with this applied in my fork on my Windows box for... too long now without any problems, my apologies for not making the PR sooner.
My work's git branch naming convention contains slashes in branch names, which causes session files tied to the branch to be unable to be created as the branch name is not escaped like the directory path is.