From 8df4e37f0dda20be0a13487f71bacf483aedaf58 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 8 Jan 2016 13:55:35 -0400 Subject: better fix for slash in view metadata The homomorphs are back, just encoded such that it doesn't crash in LANG=C However, I noticed a bug in the old escaping; [pseudoSlash] was escaped the same as ['/','/']. Fixed by using '%' to escape pseudoSlash. Which requires doubling '%' to escape it, but that's already done in the escaping of worktree filenames in a view, so is probably ok. --- .../comment_1_249d786ce15ab0c91191987c0bab76ef._comment | 3 +++ 1 file changed, 3 insertions(+) (limited to 'doc/bugs') diff --git a/doc/bugs/slash_in_metadata_breaks_field__61____42___view/comment_1_249d786ce15ab0c91191987c0bab76ef._comment b/doc/bugs/slash_in_metadata_breaks_field__61____42___view/comment_1_249d786ce15ab0c91191987c0bab76ef._comment index 2cd288951..f6fb82b51 100644 --- a/doc/bugs/slash_in_metadata_breaks_field__61____42___view/comment_1_249d786ce15ab0c91191987c0bab76ef._comment +++ b/doc/bugs/slash_in_metadata_breaks_field__61____42___view/comment_1_249d786ce15ab0c91191987c0bab76ef._comment @@ -21,4 +21,7 @@ unicode support. Sigh, 2016 and still can't have nice things.. Suppose it'll have to use an ugly encoding for them instead. + +Update: Can have nice things, just have to encode the characters using the +FileSystemEncoding! """]] -- cgit v1.2.3