# Metadata
Platforms: desktop, server OS: mac, windows, linux Introduced: 1.0 Security:
# Syntax
revUnixFromMacPath(macPathname [, convertOSX])
# Params
- macPathname : A file or folder pathname in the format used by the Mac OS for file paths. - convertOSX :
# Examples
revUnixFromMacPath("Disk:Folder:") -- returns "/Disk/Folder/"
answer file revUnixFromMacPath(someXFCN())
put revUnixFromMacPath(myValue,true)
# Description
Use the revUnixFromMacPath function to convert a Mac OS-style file path to the LiveCode file path format (for example, to convert a file path returned by an XFCN).
The revUnixFromMacPath function converts colons (:) to slashes (/), the folder-level delimiter for Unix file path. It also adjusts relative file path and absolute file path to be in Unix standard form.
On Mac OS systems, absolute paths always begin with the name of the disk that the file or folder is on. On OS X systems, the startup disk's name does not appear in absolute file paths. Instead, if a file or folder is on the startup disk, the first part of the file path is the top-level folder that the file is in. If a file or folder is on a disk other than the startup disk, its absolute path starts with "Volumes", followed by the disk name.
The OS X path convention is used by LiveCode, but the old Mac OS-style path convention is used by certain applications (such as AppleScript), even on OS X systems. If the convertOSX is true (or if you don't specify the convertOSX and the application is running under OS X), the revUnixFromMacPath function assumes that absolute file path are using the OS X convention. If the convertOSX is false, the revUnixFromMacPath function assumes that absolute paths use the Mac OS convention.
LiveCode always uses the Unix pathname standard for cross-platform compatibility. You need to convert the pathname only if you are passing it to another program or external. If you are using only LiveCode commands and functions, you do not need to convert the pathname, since LiveCode does it for you.
>*Note:* When included in a standalone application, the > Common library is implemented as a hidden group and made available > when the group receives its first openBackground message. During > the first part of the application startup process, > before this message is sent, the revUnixFromMacPath function is > not yet available. This may affect attempts to use this function in > startup, preOpenStack, openStack, or preOpenCard > handlers in the main stack. Once the application has > finished starting up, the library is available and the > revUnixFromMacPath function can be used in any handler.
# Tags
# See
- **keyword:** string - **control structure:** function - **message:** startup, openBackground, preOpenStack, openStack, preOpenCard - **command:** answer file - **library:** Common library, library - **glossary:** application, standalone application, file path, main stack, OS X, relative file path, group, absolute file path, Mac OS, message, Unix, delimiter, handler