GNU bug report logs - #29189
25.3; Dired does not work with binary filenames

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: handa <at> gnu.org, 29189 <at> debbugs.gnu.org, schwab <at> suse.de, vianchielfaura <at> gmail.com
Subject: bug#29189: 25.3; Dired does not work with binary filenames
Date: Sun, 07 Jan 2018 19:53:33 +0200

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: handa <at> gnu.org,  vianchielfaura <at> gmail.com,  29189 <at> debbugs.gnu.org,  schwab <at> suse.de
> Date: Sun, 07 Jan 2018 10:20:06 -0500
> 
> > Input that is from multibyte text can include raw bytes in their
> > multibyte representation.  What is a "non-byte"?
> 
> `λ`?  `é`?  `²`?

These are characters, so they will never end up in the code fragment
that was the subject of this big, because that code deals specifically
with the unprocessed tail of byte stream that could not be decoded.
They will be decoded with the rest of the text before we get to the
code being discussed.

And even if you would like to add there assertion for "cannot happen"
stuff, how would you identify such "non-bytes"?  Their byte sequences
depend on the original encoding, so detecting them sounds like your
favorite Turing stopping problem, no?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.