[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Multibyte and unibyte file names
From: |
Eli Zaretskii |
Subject: |
Re: Multibyte and unibyte file names |
Date: |
Thu, 24 Jan 2013 19:02:22 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, Kazuhiro Ito <address@hidden>,
> Michael Albinus <address@hidden>
> Date: Wed, 23 Jan 2013 16:09:18 -0500
>
> I think that for w32 it makes sense to try and always decode file names
> before returning them to Elisp:
> Most file names passed to Elisp primitives are derived from file names
> returned by Elisp primitives, so if Emacs decodes all the file names it
> returns to Elisp, we can expect to see *very* few encoded file names
> passed to Elisp primitives.
So you are saying that each primitive should detect unibyte file names
it gets as arguments and DECODE_FILE them right away? We would also
need to modify all the C code that calls the primitives directly and
passes them encoded file names. Did I understand your suggestion
correctly?
- Multibyte and unibyte file names, Eli Zaretskii, 2013/01/23
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/23
- Re: Multibyte and unibyte file names,
Eli Zaretskii <=
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/24
- Re: Multibyte and unibyte file names, Eli Zaretskii, 2013/01/24
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/24
- Re: Multibyte and unibyte file names, Eli Zaretskii, 2013/01/25
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/25
- Re: Multibyte and unibyte file names, Eli Zaretskii, 2013/01/25
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/25
- Re: Multibyte and unibyte file names, Eli Zaretskii, 2013/01/26
- Re: Multibyte and unibyte file names, Stefan Monnier, 2013/01/26
- Re: Multibyte and unibyte file names, Eli Zaretskii, 2013/01/26