[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "*** INTERNAL: readdir: Invalid argument" error
From: |
David Boyce |
Subject: |
Re: "*** INTERNAL: readdir: Invalid argument" error |
Date: |
Wed, 15 May 2013 08:07:55 -0700 |
On Wed, May 15, 2013 at 7:54 AM, Eli Zaretskii <address@hidden> wrote:
> because of the need to convert the file names from UTF-16 to
> something the rest of the code can grok.
Well, if I understand correctly there's no need to actually grok the
UTF-16 filenames, just to get past them with a more graceful failure
condition, and I was hoping these other APIs would fail differently.
But if you say there's no joy here I believe it.
> In any case, there's no reason to use any of this just to check
> whether a file by a specific name exists in a directory.
Are you saying you'd just walk along PATH doing a stat() or access()
or equivalent on <dir>/sh.exe?
David
- "*** INTERNAL: readdir: Invalid argument" error, Eli Zaretskii, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, Paul Smith, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, David Boyce, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, Eli Zaretskii, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error,
David Boyce <=
- Re: "*** INTERNAL: readdir: Invalid argument" error, Eli Zaretskii, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, Edward Welbourne, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, Paul Smith, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, David Boyce, 2013/05/15
- Re: "*** INTERNAL: readdir: Invalid argument" error, Eli Zaretskii, 2013/05/15