@J-Dunn: no, this PR only fixes the issue which #779 directly addresses. As 
@elextr wrote the path encoding in the config file is correct. It only would be 
a bug if you see such enocidng in an output.

@elextr: no, only purely changed what PR #779 addresses and won't do anything 
else in this PR.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Reply via email to