Work around problem with concurrent-output when in a non-unicode locale by avoiding use of it in such a locale.

Instead -J will behave as if it was built without concurrent-output support
in this situation. Ie, it will be mostly quiet, except when there's an
error.

Note that it's not a problem for a filename to contain invalid utf-8 when
in a utf-8 locale. That is handled ok by concurrent-output. It's only
displaying unicode characters in a non-unicode locale that doesn't work.
This commit is contained in:
Joey Hess 2016-02-14 15:02:42 -04:00
parent d3130930db
commit 0f18636c8a
Failed to extract signature
8 changed files with 82 additions and 45 deletions

View file

@ -81,3 +81,8 @@ Plenty. In fact I've been using it for a long time - I just only recently tried
[[!meta title="-J can crash on displaying filenames not supported by current locale"]]
> I've worked around this by detecting the non-unicode locale and avoiding
> the fancy concurrent output which needs it. So -J will work, just not
> with concurrent progress. I think this is the best that can be done
> reasonably, so [[done]]. --[[Joey]]