![]() ![]() ![]() If there are space characters or other special characters in the POSIX path, the characters must be escaped (with backslash) or the path must be quoted. In the shell, all paths are POSIX paths (slash separated). In AppleScript all paths are HFS path (colon separated). “:Volumes:Hard Disk:Folder:” doesn’t work). Here’s a sample path that is hell for me using TID replacement:Īlso, how do you handle the extra “/Volumes/” that the shell wants, but AppleScript gets confused by as an alias? (i.e. I’m currently using Option 1 with problems with “/” is filenames. When your coworker gets it, they click the link in the email and it should open the folder in Finder (assuming they have the SMB server currently connected). As the link address, put in the file path. Make the path a link - this will vary between email clients. Obviously Option 2 is preferred and cleaner. You can copy the path using Edit > Copy or Command+C. Not illegal in Mac Finder, but causes havoc with using the TID trick (covert “/” to “:” and the reverse). I had written some routines to covert between paths and aliases as needed using ASTIDs, but I ran into a problem when users decide to put slashes in the file names. If there is some on-the-fly coersion that will work with special characters and “/” characters (escaping everything properly), love to see it! For example “number of items in folder folder_to_check” does not work when “folder_to_check” is a shell path, only seems to accept an alias (colon-delimited path). How to get Finder commands to cooperate with shell-style (slash-delimited) paths. Must keep escaped characters in mind (like “/”) and special characters intact in both directions. How to covert a shell path to an alias, and then an alias back to a path. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |