Re:Become Shell Literate
by CJefferson on Saturday December 12, 2020 @01:25PM
(#25400299)
This would require filenames became valid utf-8. This would be a good thing to do nowadays, irritatingly (having tried handling Unix filenames as utf 8 in the past), surprisingly many users have non-utf8 filenames.
[ Parent
| on HN ]
Re:Become Shell Literate
by a1369209993 on Saturday December 12, 2020 @07:48PM
(#25403263)
> This would require filenames became valid utf-8.
No, it wouldn't; you'd just get EINVAL if you pass a filename containing "\x20" to open or other syscalls. If a application wants to use "\xC2\xA0" in a filename, it can do that, or it can not do that, same as currently. Same applies if it wants to use, say, "\xAA\xFF".