summaryrefslogtreecommitdiff
path: root/doc/bugs/Unable_to_parallel_fsck.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-02-14 15:02:42 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-02-14 15:02:42 -0400
commitb9c249d46e582bf52b771368cfe9d8d455c11f9f (patch)
treed80ac8add3a7c560a8ec8cb148d6e1ae2effbe9e /doc/bugs/Unable_to_parallel_fsck.mdwn
parentcc13dd82c5cd7647f911ed6be1e58694f7edee31 (diff)
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.
Diffstat (limited to 'doc/bugs/Unable_to_parallel_fsck.mdwn')
-rw-r--r--doc/bugs/Unable_to_parallel_fsck.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/Unable_to_parallel_fsck.mdwn b/doc/bugs/Unable_to_parallel_fsck.mdwn
index 2d419915d..487552f54 100644
--- a/doc/bugs/Unable_to_parallel_fsck.mdwn
+++ b/doc/bugs/Unable_to_parallel_fsck.mdwn
@@ -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]]