Re: Not Resolving Aliases

2009-01-27 Thread Scott Ribe
> I would expect the > documentation to call out the fact that a routine *does* automatically > resolve leaf symlinks. That would be my preference, but it hasn't always been so... -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice

Re: Not Resolving Aliases

2009-01-27 Thread Jean-Daniel Dupas
Le 27 janv. 09 à 12:25, Jean-Daniel Dupas a écrit : Le 27 janv. 09 à 12:03, Gregory Weston a écrit : Scott Ribe wrote: I have given up on NSWorkspace, LaunchServices and now send the path via Distributed Objects. Hey, that surprises me ;-) Give what you said, my next attempt would ha

Re: Not Resolving Aliases

2009-01-27 Thread Jean-Daniel Dupas
Le 27 janv. 09 à 12:03, Gregory Weston a écrit : Scott Ribe wrote: I have given up on NSWorkspace, LaunchServices and now send the path via Distributed Objects. Hey, that surprises me ;-) Give what you said, my next attempt would have been constructing an open Apple Event... (Don't know i

Re: Not Resolving Aliases

2009-01-27 Thread Gregory Weston
Scott Ribe wrote: I have given up on NSWorkspace, LaunchServices and now send the path via Distributed Objects. Hey, that surprises me ;-) Give what you said, my next attempt would have been constructing an open Apple Event... (Don't know if it would work, because I don't know when the norm

Re: Not Resolving Aliases

2009-01-26 Thread Gerriet M. Denkmann
On 27 Jan 2009, at 11:05, Scott Ribe wrote: I have given up on NSWorkspace, LaunchServices and now send the path via Distributed Objects. Hey, that surprises me ;-) Give what you said, my next attempt would have been constructing an open Apple Event... (Don't know if it would work, because

Re: Not Resolving Aliases

2009-01-26 Thread Scott Ribe
> I have given up on NSWorkspace, LaunchServices and now send the path > via Distributed Objects. Hey, that surprises me ;-) Give what you said, my next attempt would have been constructing an open Apple Event... (Don't know if it would work, because I don't know when the normal resolution of syml

Re: Not Resolving Aliases

2009-01-26 Thread Gerriet M. Denkmann
On 27 Jan 2009, at 07:39, Scott Ribe wrote: What are you actually trying to do? I was trying to send the path of a symbolic link (not the content of this link, which anyway might not exist) to another app. This other app displays all sort of information or metadata about this path. Th

Re: Not Resolving Aliases

2009-01-26 Thread Scott Ribe
What are you actually trying to do? -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list.

Re: Not Resolving Aliases

2009-01-25 Thread Gerriet M. Denkmann
On 25 Jan 2009, at 09:31, Michael Ash wrote: On Sat, Jan 24, 2009 at 9:54 AM, Gerriet M. Denkmann wrote: When I do: [ sharedWorkspace openFile: @"/path/to/symlink" withApplication: @"SomeApp" ] then "SomeApp" does NOT get "/path/to/symlink" but the content of the symlink. Same for Al

Re: Not Resolving Aliases

2009-01-24 Thread Michael Ash
On Sat, Jan 24, 2009 at 9:54 AM, Gerriet M. Denkmann wrote: > > When I do: > > [ sharedWorkspace openFile: @"/path/to/symlink" withApplication: @"SomeApp" > ] > > then "SomeApp" does NOT get "/path/to/symlink" but the content of the > symlink. > Same for Aliases. > > Is there a way to open a path

Not Resolving Aliases

2009-01-24 Thread Gerriet M. Denkmann
When I do: [ sharedWorkspace openFile: @"/path/to/symlink" withApplication: @"SomeApp" ] then "SomeApp" does NOT get "/path/to/symlink" but the content of the symlink. Same for Aliases. Is there a way to open a path without resolving aliases? Kind regards, Gerriet. __