-
Notifications
You must be signed in to change notification settings - Fork 14
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
Special characters in filenames are not properly encoded #110
Comments
hmm thanks. I was able to reproduce but when I added unit tests, they pass. e.g.
|
The problem is the git commands. I'll keep looking at this $ npm run sb
$ cd sandbox
$ git add sp*
$ git ls
README.md
bazz.js
buzz.js
fizz.js
foo.js
"sp\303\253cial ch\303\242racters.md" |
Can you do this in your repo or globally across repos with
Then try again and let me know if that works? I started implementing a fix in the code but it touched a couple of files and then at some point the sandbox won't start beacuse of some error in vs code so I am stuck for now |
@MichaelCurrin With git -c 'core.quotePath=false' ls-files |
I've pushed the change on master if you want to build and install locally git clone ... I am not going to publish the change yet as a new version of the extension |
Hi, I've published a new version |
Nice, but for me the new version throws this error (on Windows)
Running the command from the error message works as expected in Powershell… |
In CMD I can recreate the error:
Using double quotes or no quotes at all works though EDIT: Single Quotes in CMD are just regular characters, so it is expected to not work in cmd |
@MichaelCurrin I prepared #114 with a fix And by now I am sorry that I did not build the earlier version myself and test it. Then the (on Windows) broken release could have been prevented :/ |
If filenames contain non-ASCII characters this can lead to unexpected commit message suggestions. See for example this screenshot:
The text was updated successfully, but these errors were encountered: