-
Notifications
You must be signed in to change notification settings - Fork 111
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
create-sibling: Use C.UTF-8 locale instead of C #7273
create-sibling: Use C.UTF-8 locale instead of C #7273
Conversation
- supports special characters in filenames (like umlauts, etc.) - `ls` seems to fall back to predictable `C` locale if `LC_ALL` is set to an unknown locale, so this should be safe. - still: `create-sibling` currently fails silently if an umlaut is in the `--target-dir` and the remote `ls` doesn't handle it properly. follow-up on PR datalad#7265
Codecov ReportBase: 88.71% // Head: 90.71% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## maint #7273 +/- ##
==========================================
+ Coverage 88.71% 90.71% +1.99%
==========================================
Files 326 326
Lines 44427 44429 +2
Branches 5919 5919
==========================================
+ Hits 39414 40303 +889
+ Misses 4998 4111 -887
Partials 15 15
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Thanks, @nobodyinperson! I think this is fine. |
I wonder if this would not kick-back on systems/environments without UTF-8 support available somehow (may be some really minimalistic environment/filesystem) but I guess we will see. Thanks @nobodyinperson ! |
PR released in |
ls
seems to fall back to predictableC
locale ifLC_ALL
is set to an unknown locale, so this should be safe.create-sibling
currently fails silently if an umlaut is in the--target-dir
and the remotels
doesn't handle it properly.follow-up on PR #7265