Path Finder

I bought a copy of Toast with Jam. It is working for me. I need to do more tests and time them. I think the finder may be burning just as fast. ...

You'd think that user A wouldn't be able to access the file he put in the drop box - after all, shouldn't a drop box be write-only? But because of limitations of the user/group/other read/write/execute permissions that OS X uses, that cannot be implemented easily. The drop box will have permissions write and execute for others, but no read. This allows users to create files...

That is, of course, if you're using bash. If you use csh or tcsh, then you need to edit the .cshrc (or create it) in your home directory. The syntax for adding paths is different, too, so don't just copy and paste the above line into the .cshrc file.

add: PATH=${PATH}:~/Applications to your .bash_profile in your home directory, beware that files beginning with a dot are invisible in the Finder, if you don't have a .bash_profile you can create one yourself

I want to make an apple script that mounts a disk image, and then opens an application. However when I try to tell finder to open file, I get an error saying can't get file. I finally got it to work using the do shell script open command, but this seems rather kludgy to me. ...

Go to Folder" and choose the unix path and a Finder folder will open up to it. Also, you could download TinkerTool. When running the program you can have invisible Folders and Files shown. ...

drop a file or folder onto the terminal window to "type" its full path and filename into a terminal. You can also use the "open" command in the terminal to open files or applications, even when you're logged in remotely via SSH. ...

dragging, you can put folder in the left navigation bar of Finder Windows etc. etc. The environment works with you not against you. ...

etc which you can't see in the Finder unless you type in the path directly into the Open Folder command. ...

Excellent. I thought much of the article was fluff though (I wonder if this Ted Landau gets a little kickback). Half of it seemed to be a product ad and manual. Nonetheless it got to the point (albeit fuzzy with drag'n'drop blab) with the SetFile command from the OSX Developer Tools. Thanks. For anybody not wanting to go through the torture, here is how to hide a file...