-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Progress Handler incompatible with non-English locales #579
Comments
Hi, looks great in the video. The published version supports any stage in the RegExp - https://github.com/steveukx/git-js/blob/v2.35.0/src/lib/plugins/progress-monitor-plugin.ts#L18, so as long as the non-english locale conforms to the format I see in your pull request, you're using |
Hi @steveukx, and thanks for your quick reply! (And a great tool!)
Ah, right! Seems like I was looking at the wrong RegEx 😅
Hmm, I actually meant to use the progress handler for the Anyway, looks like this issue can be closed! 😄 |
Progress plugin does not work for Russian locale for git clone command. In my case, Git clone output contains Cyrillic symbols (output is This issue affect any non-English locale. |
@zlocate thanks for pointing this out - the new version 2.45.1 will support non-english characters. |
The new progress handler feature (in v2.35.0) is great -- thanks a lot for implementing it!
Here's a video of it in action. Note that while implementing this change, I found that it didn't work on my own system, whereas it worked for my coworker. I suspect that the reason is that my locale is set to German, and the RegEx that's looking for progress messages is "hard-wired" to an English progress message (
Receiving objects:
) -- which it can't find ingit
's German-language output on my system (would beEmpfange Objekte:
for me). (My coworker's locale is set to English.)Would it be possible to force English by setting an environment variable (e.g.
LC_ALL=C
) when spawninggit
, in order to make the progress handler work?The text was updated successfully, but these errors were encountered: