[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: filename coding systems and w32-*-file-name functions
From: |
Juanma Barranquero |
Subject: |
Re: filename coding systems and w32-*-file-name functions |
Date: |
Thu, 27 Nov 2008 21:24:21 +0100 |
On Thu, Nov 27, 2008 at 20:53, Eli Zaretskii <address@hidden> wrote:
> This cannot be right, since DECODE_FILE produces a Lisp_Object,
> whereas build_string takes a "char *" argument. That's why you need
> SDATA.
A transcription error; in the patch I have the SDATA.
But still I don't know why I do need build_string (SDATA (DECODE_FILE
(build_string (longname))));
Juanma
- filename coding systems and w32-*-file-name functions, Juanma Barranquero, 2008/11/24
- Re: filename coding systems and w32-*-file-name functions, martin rudalics, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Jason Rumney, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Juanma Barranquero, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Jason Rumney, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Juanma Barranquero, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Eli Zaretskii, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions,
Juanma Barranquero <=
- Re: filename coding systems and w32-*-file-name functions, Eli Zaretskii, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Juanma Barranquero, 2008/11/27
- Re: filename coding systems and w32-*-file-name functions, Eli Zaretskii, 2008/11/28
- Re: filename coding systems and w32-*-file-name functions, Juanma Barranquero, 2008/11/29