unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 29189@debbugs.gnu.org, vianchielfaura@gmail.com, schwab@suse.de
Subject: bug#29189: 25.3; Dired does not work with binary filenames
Date: Sat, 06 Jan 2018 18:04:56 +0200	[thread overview]
Message-ID: <83608f9dnb.fsf@gnu.org> (raw)
In-Reply-To: <jwvbmi72fak.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 06 Jan 2018 10:20:38 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: handa@gnu.org,  vianchielfaura@gmail.com,  29189-don@debbugs.gnu.org,  schwab@suse.de
> Date: Sat, 06 Jan 2018 10:20:38 -0500
> 
> > Situations where file names are not valid byte sequences for the
> > locale's codeset are rare.
> 
> Hmm... then I think I have misunderstood something: why doesn't this
> problem show up with a valid name like "λ" ?

Because "λ" will be inserted by 'ls' as a valid UTF-8 sequence of raw
bytes, and will be correctly decoded.  By contrast, \265 is not a
valid UTF-8 sequence, so we need it to produce a string of a single
raw byte.

> >> I'd also be tempted to additionally signal an error if a non-byte
> >> (i.e. a char that's neither ASCII nor eight-bit-byte) is found since
> >> "decoding" in that case is meaningless.
> > I don't think I understand.  A given byte sequence can either
> > represent a decodable character or be a raw byte.  What third
> > possibility did you have in mind?
> 
> If the input is from a multibyte text, the input is not a byte sequence
> but a character sequence, so the third possibility is to have a non-byte
> in those characters.

Input that is from multibyte text can include raw bytes in their
multibyte representation.  What is a "non-byte"?





  parent reply	other threads:[~2018-01-06 16:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  9:03 bug#29189: 25.3; Dired does not work with binary filenames Allen Li
2017-11-07 10:00 ` Andreas Schwab
2017-11-07 17:08   ` Eli Zaretskii
2017-11-08  5:12     ` Allen Li
2017-11-08  6:22   ` Allen Li
2017-11-08  8:44     ` Eli Zaretskii
2017-11-11  6:59       ` Allen Li
2017-11-11  8:20         ` Eli Zaretskii
2017-11-11 14:18           ` Eli Zaretskii
2017-11-11 15:21             ` Eli Zaretskii
2017-11-16  6:31               ` Allen Li
2017-11-16 16:00                 ` Eli Zaretskii
2017-11-18 14:42                   ` Eli Zaretskii
2017-11-20  9:48                     ` Andreas Schwab
2017-11-20 18:15                       ` Eli Zaretskii
2017-11-24  8:52                         ` Eli Zaretskii
2017-12-01  8:41                           ` Eli Zaretskii
2017-12-09  9:03                             ` Eli Zaretskii
2017-12-15  9:09                               ` Eli Zaretskii
2017-12-02  5:21                         ` Allen Li
2017-12-02  9:01                           ` Eli Zaretskii
2018-01-05 22:16                     ` Stefan Monnier
     [not found]                       ` <83h8rz9x6k.fsf@gnu.org>
     [not found]                         ` <jwvbmi72fak.fsf-monnier+emacs@gnu.org>
2018-01-06 16:04                           ` Eli Zaretskii [this message]
2018-01-07 15:20                             ` Stefan Monnier
2018-01-07 17:53                               ` Eli Zaretskii
     [not found] <CADbSrJytKAysg4DRNR4iJD5JJbn7iwi_28Gh_oabaE-rnVyqLw@mail.gmail.com>
2018-09-09  0:31 ` Allen Li
2018-09-09  6:12   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83608f9dnb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29189@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@suse.de \
    --cc=vianchielfaura@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).