Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread Michael Vannorsdel
How are you invoking rsync? With NSTask or system()? On May 16, 2008, at 8:28 AM, JanakiRam wrote: When i give this filename as part of rsync source file ( using -- files-from ) , rsync is treating this filename as 2 different file names , because rsync expects each filen name separated by

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread Jens Alfke
On 16 May '08, at 7:28 AM, JanakiRam wrote: When i give this filename as part of rsync source file ( using -- files-from ) , rsync is treating this filename as 2 different file names , because rsync expects each filen name separated by \r. Then it sounds like the author of rsync didn't tak

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread Hamish Allan
On Fri, May 16, 2008 at 3:28 PM, JanakiRam <[EMAIL PROTECTED]> wrote: > When i give this filename as part of rsync source file ( using --files-from > ) , rsync is treating this filename as 2 different file names , because > rsync expects each filen name separated by \r. > Hence my rsync command is

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread JanakiRam
When i give this filename as part of rsync source file ( using --files-from ) , rsync is treating this filename as 2 different file names , because rsync expects each filen name separated by \r. Hence my rsync command is failing JanakiRam. On Fri, May 16, 2008 at 5:42 PM, Jean-Daniel Dupas <

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread Hamish Allan
On Fri, May 16, 2008 at 6:02 AM, JanakiRam <[EMAIL PROTECTED]> wrote: > When i perform ls command it shows file name as "Icon?". When i perform cp > command & tab it shows the file name as "Icon^M". > Why Terminal does show different names for the same file. Because the filename contains a non-pr

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-16 Thread Jean-Daniel Dupas
Yes, they all display it in a different way, and why is it a problem ? What does it prevent you to do? Le 16 mai 08 à 07:02, JanakiRam a écrit : When i perform ls command it shows file name as "Icon?". When i perform cp command & tab it shows the file name as "Icon^M". Why Terminal does s

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-15 Thread JanakiRam
When i perform ls command it shows file name as "Icon?". When i perform cp command & tab it shows the file name as "Icon^M". Why Terminal does show different names for the same file. When i see it in Finder it does show as "Icon". Please advise. Thanks in Advance. JanakiRam On Thu, May 15, 2008

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-15 Thread Michael Vannorsdel
This has to do with non-printable characters in pathnames. Each application can different how they visually represent these characters. The terminal just replaces them with '?', the Finder might use a space. When you have a path from NSFileManager, leave it as is in the NSString if you'

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-15 Thread Graham Cox
How do the two outputs differ from your expectations? G. On 15 May 2008, at 8:17 pm, JanakiRam wrote: But its very important for me to fix. Please help me. My application is trying to enumerate the folders in inside a Mac using NSFileManager API. But for some files its failing. It looks l

Re: Problem with NSFileManger directoryContentsAtPath

2008-05-15 Thread Jean-Daniel Dupas
"Icon\r" is an invisible file that contains a custom directory icon. What make you think this file is handle in different way ? The terminal displays '\r' as ^M but it's not a problem. Isn't it? Le 15 mai 08 à 12:17, JanakiRam a écrit : Hi All, I'm facing an issue with NSFileManger directoryC