Rob McBroom wrote:
On Nov 15, 2007, at 11:04 AM, dzurn wrote:
The `open` command will handle local files just fine without the "file://" protocol specified. This worked for me to open `textmate.pdf`:
open "/Users/rob/Documents/Books/textmate"*Note that the * wild-card is interpreted by the shell and the result is then passed to `open`. Your shell doesn't see any files named "file://something", so it bails. Basically, the * means nothing to the `open` command and "file://" means nothing to your shell. A plain old file path is something they both understand, which is why the above command works.
Rob McBroom
Odd. I couldn't get the open command to work without the file:// protocol. However, I found that the problem I was having was due to my encoding the spaces as "%20" in the open command. Once I got rid of the file:// and the %20 (replaced with spaces) then the * wildcard would work.
Thanks a lot! Darryl Zurn