P4v      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuSafeHvunstableportableSafezwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Safe$8POSIX: either file or directory link; Windows: file link  Windows only  Similar to M$ but only catches a specify kind of s" as specified by the predicate.Check whether the given i is considered a directory by the operating system. This affects the choice of certain functions e.g. removeDirectory vs  removeFile.9Obtain the current working directory as an absolute path. In a multithreaded program, the current working directory is a global state shared among all threads of the process. Therefore, when performing filesystem operations from multiple threads, it is highly recommended to use absolute rather than relative paths (see:  makeAbsolute).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]E or  NoSuchThing8 There is no path referring to the working directory. [EPERM, ENOENT, ESTALE...]C or PermissionDeniedE The process has insufficient privileges to perform the operation. [EACCES]ResourceExhausted@ Insufficient resources are available to perform the operation.fB The operating system has no notion of current working directory.Convert a path into an absolute path. If the given path is relative, the current directory is prepended. If the path is already absolute, the path is returned unchanged. The function preserves the presence or absence of the trailing path separator.|If the path is already absolute, the operation never fails. Otherwise, the operation may fail with the same exceptions as .(internal API)   Safe%I !"#$%&Safe%'()*+,'(unstable unportableSafe&-   !"#$%&'()*+,-   !"#$%&'(*+,)"(c) The University of Glasgow 2001/BSD-style (see the file libraries/base/LICENSE)libraries@haskell.orgstableportableSafe1C-BSearch paths for various application data, as specified by the  Fhttp://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification.Note: On Windows, . and / yield the same result..-For data files (e.g. images). Defaults to usrlocalshare and usrshare/! and can be overridden by the  XDG_DATA_DIRS, environment variable. On Windows, it is  %PROGRAMDATA% or %ALLUSERSPROFILE% (e.g. C:/ProgramData)./(For configuration files. Defaults to etcxdg! and can be overridden by the XDG_CONFIG_DIRS, environment variable. On Windows, it is  %PROGRAMDATA% or %ALLUSERSPROFILE% (e.g. C:/ProgramData).0zSpecial directories for storing user-specific application data, configuration, and cache files, as specified by the  Fhttp://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification.Note: On Windows, 1 and 2 map to the same directory.1-For data files (e.g. images). Defaults to ~/.local/share! and can be overridden by the  XDG_DATA_HOME, environment variable. On Windows, it is  %APPDATA% (e.g.  C:/Users/<user>/AppData/Roaming;). Can be considered as the user-specific equivalent of  /usr/share.2(For configuration files. Defaults to  ~/.config! and can be overridden by the XDG_CONFIG_HOME, environment variable. On Windows, it is  %APPDATA% (e.g.  C:/Users/<user>/AppData/Roaming;). Can be considered as the user-specific equivalent of /etc.35For non-essential files (e.g. cache). Defaults to ~/.cache! and can be overridden by the XDG_CACHE_HOME, environment variable. On Windows, it is %LOCALAPPDATA% (e.g.  C:/Users/<user>/AppData/Local;). Can be considered as the user-specific equivalent of  /var/cache.A generator with side-effects.9+Get the permissions of a file or directory.On Windows, the < permission corresponds to the "read-only" attribute. The N permission is set if the file extension is of an executable file type. The  permission is always set.-On POSIX systems, this returns the result of access.The operation may fail with:C> if the user is not permitted to access the permissions, orE) if the file or directory does not exist.:+Set the permissions of a file or directory.1On Windows, this is only capable of changing the m permission, which corresponds to the "read-only" attribute. Changing the other permissions has no effect. On POSIX systems, this sets the owner permissions.The operation may fail with:C; if the user is not permitted to set the permissions, orE) if the file or directory does not exist.;jCopy the permissions of one file to another. This reproduces the permissions more accurately than using 9 followed by :.5On Windows, this copies only the read-only attribute.(On POSIX systems, this is equivalent to stat followed by chmod.<< dir creates a new directory dirN which is initially empty, or as near to empty as the operating system allows.The operation may fail with:C / PermissionDeniedC The process has insufficient privileges to perform the operation. [EROFS, EACCES]F /  AlreadyExists8 The operand refers to a directory that already exists.  [EEXIST] HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument, The operand is not a valid directory name. [ENAMETOOLONG, ELOOP] NoSuchThing$ There is no path to the directory. [ENOENT, ENOTDIR]ResourceExhausted Insufficient resources (virtual memory, process file descriptors, physical disk space, etc.) are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]e6 The path refers to an existing non-directory object. [EEXIST]== parents dir creates a new directory dir/ if it doesn't exist. If the first argument is K the function will also create all parent directories if they are missing.>> dir removes an existing directory dir. The implementation may specify additional constraints which must be satisfied before a directory can be removed (e.g. the directory has to be empty, or may not be in use by other processes). It is not legal for an implementation to partially remove a directory unless the entire directory is removed. A conformant implementation need not support directory removal in all situations (e.g. removal of the root directory).The operation may fail with: HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument, The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]E /  NoSuchThing The directory does not exist. [ENOENT, ENOTDIR]C / PermissionDeniedC The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]f@ The implementation does not support removal in this situation. [EINVAL]e9 The operand refers to an existing non-directory object.  [ENOTDIR]?? dir removes an existing directory dir together with its contents and subdirectories. Within this directory, symbolic links are removed without affecting their targets.#On Windows, the operation fails if dir is a directory symbolic link. path+ removes an existing file or directory at pathp together with its contents and subdirectories. Symbolic links are removed without affecting their the targets. dir( removes the contents of the directory dirN recursively. Symbolic links are removed without affecting their the targets.@Removes a file or directory at path together with its contents and subdirectories. Symbolic links are removed without affecting their targets. If the path does not exist, nothing happens.oUnlike other removal functions, this function will also attempt to delete files marked as read-only or otherwise made unremovable due to permissions. As a result, if the removal is incomplete, the permissions or attributes on the remaining files may be altered. If there are hard links in the directory, then permissions on all related hard links may be altered.0If an entry within the directory vanishes while removePathForcibly% is running, it is silently ignored.0If an exception occurs while removing an entry, removePathForcibly will still try to remove as many entries as it can before failing with an exception. The first exception that it encountered is re-thrown.AA file2 removes the directory entry for an existing file file, where file is not itself a directory. The implementation may specify additional constraints which must be satisfied before a file can be removed (e.g. the file may not be in use by other processes).The operation may fail with: HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument' The operand is not a valid file name. [ENAMETOOLONG, ELOOP]E /  NoSuchThing The file does not exist. [ENOENT, ENOTDIR]C / PermissionDeniedC The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY]e. The operand refers to an existing directory. [EPERM, EINVAL]BB old new0 changes the name of an existing directory from old to new . If the new< directory already exists, it is atomically replaced by the old directory. If the new directory is neither the old directory nor an alias of the old# directory, it is removed as if by >. A conformant implementation need not support renaming directories in all situations (e.g. renaming to an existing directory, or across different physical devices), but the constraints must be documented.On Win32 platforms, renameDirectory fails if the new directory already exists.The operation may fail with: HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument/ Either operand is not a valid directory name. [ENAMETOOLONG, ELOOP]E /  NoSuchThingK The original directory does not exist, or there is no path to the target. [ENOENT, ENOTDIR]C / PermissionDeniedC The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]ResourceExhausted@ Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]fA The implementation does not support renaming in this situation. [EINVAL, EXDEV]e9 Either path refers to an existing non-directory object. [ENOTDIR, EISDIR]CC old new9 changes the name of an existing file system object from old to new . If the new9 object already exists, it is atomically replaced by the old object. Neither path may refer to an existing directory. A conformant implementation need not support renaming files in all situations (e.g. renaming across different physical devices), but the constraints must be documented.The operation may fail with: HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument* Either operand is not a valid file name. [ENAMETOOLONG, ELOOP]E /  NoSuchThingF The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]C / PermissionDeniedC The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]ResourceExhausted@ Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY]fA The implementation does not support renaming in this situation. [EXDEV]e. Either path refers to an existing directory. ,[ENOTDIR, EISDIR, EINVAL, EEXIST, ENOTEMPTY]DLRename a file or directory. If the destination path already exists, it is replaced atomically. The destination path must not point to an existing directory. A conformant implementation need not support renaming files in all situations (e.g. renaming across different physical devices), but the constraints must be documented.The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument, Either operand is not a valid file name. [ENAMETOOLONG, ELOOP]E /  NoSuchThingH The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]C / PermissionDeniedE The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]ResourceExhaustedB Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints; Implementation-dependent constraints are not satisfied. [EBUSY]fC The implementation does not support renaming in this situation. [EXDEV]e Either the destination path refers to an existing directory, or one of the parent segments in the destination path is not a directory. ,[ENOTDIR, EISDIR, EINVAL, EEXIST, ENOTEMPTY]ECopy a file with its permissions. If the destination file already exists, it is replaced atomically. Neither path may refer to an existing directory. No exceptions are thrown if the permissions could not be copied.Truncate the destination file and then copy the contents of the source file to the destination file. If the destination file already exists, its attributes shall remain unchanged. Otherwise, its attributes are reset to the defaults.iCopy the contents of a source file to a destination file, replacing the destination file atomically via D, resetting the attributes of the destination file to the defaults.A helper function useful for replacing files in an atomic manner. The function creates a temporary file in the directory of the destination file, opens it, performs the main action with its handle, closes it, performs the post-action with its path, and finally replaces the destination file with the temporary file. If an error occurs during any step of this process, the temporary file is removed and the destination file remains untouched.NAttempt to perform the given action, silencing any IO exception thrown by it.&Copy all data from a file to a handle.7Copy data from one handle to another until end of file.FTCopy a file with its associated metadata. If the destination file already exists, it is overwritten. There is no guarantee of atomicity in the replacement of the destination file. Neither path may refer to an existing directory. If the source and/or destination are symbolic links, the copy is performed on the targets of the links.0On Windows, it behaves like the Win32 function  Fhttps://msdn.microsoft.com/en-us/library/windows/desktop/aa363851.aspxCopyFilef, which copies various kinds of metadata including file attributes and security resource properties.2On Unix-like systems, permissions, access time, and modification time are preserved. If possible, the owner and group are also preserved. Note that the very act of copying can change the access time of the source file, hence the access times of the two files may differ after the operation completes.GMake a path absolute, r the path, and remove as many indirections from it as possible. Any trailing path separators are discarded via J. Additionally, on Windows the letter case of the path is canonicalized.NoteK: This function is a very big hammer. If you only need an absolute path, HI is sufficient for removing dependence on the current working directory.1Indirections include the two special directories . and ..b, as well as any symbolic links (and junction points on Windows). The input path need not point to an existing file or directory. Canonicalization is performed on the longest prefix of the path that points to an existing file or directory. The remaining portion of the path that does not point to an existing file or directory will still undergo u, but case canonicalization and indirection removal are skipped as they are impossible to do on a nonexistent path.Most programs should not worry about the canonicity of a path. In particular, despite the name, the function does not truly guarantee canonicity of the returned path due to the presence of hard links, mount points, etc.If the path points to an existing file or directory, then the output path shall also point to the same file or directory, subject to the condition that the relevant parts of the file system do not change while the function is still running. In other words, the function is definitively not atomic. The results can be utterly wrong if the portions of the path change while this function is running.8Since some indirections (symbolic links on all systems, .. on non-Windows systems, and junction points on Windows) are dependent on the state of the existing filesystem, the function can only make a conservative attempt by removing such indirections from the longest prefix of the path that still points to an existing file or directory.(Note that on Windows parent directories ..p are always fully expanded before the symbolic links, as consistent with the rest of the Windows API (such as GetFullPathName6). In contrast, on POSIX systems parent directories ..\ are expanded alongside symbolic links from left to right. To put this more concretely: if L is a symbolic link for R/P, then on Windows L\.. refers to .%, whereas on other operating systems L/.. refers to R. Similar to H, passing an empty path is equivalent to passing the current directory.canonicalizePath can resolve at least 64 indirections in a single path, more than what is supported by most operating systems. Therefore, it may return the fully resolved path even though the operating system itself would have long given up.\On Windows XP or earlier systems, junction expansion is not performed due to their lack of GetFinalPathNameByHandle.Changes since 1.2.3.0:Y The function has been altered to be more robust and has the same exception behavior as H.Changes since 1.3.0.0: The function no longer preserves the trailing path separator. File symbolic links that appear in the middle of a path are properly dereferenced. Case canonicalization and symbolic link expansion are now performed on Windows.HConvert a path into an absolute path. If the given path is relative, the current directory is prepended and then the combined result is 9d. If the path is already absolute, the path is simply d. The function preserves the presence or absence of the trailing path separator unless the path refers to the root directory /.|If the path is already absolute, the operation never fails. Otherwise, the operation may fail with the same exceptions as .lAdd or remove the trailing path separator in the second path so as to match its presence in the first path.(internal API)I@Construct a path relative to the current directory, similar to .3The operation may fail with the same exceptions as .J.Given the name or path of an executable file, J\ searches for such a file in a list of system-defined locations, which generally includes PATHZ and possibly more. The full path to the executable is returned if found. For example, (findExecutable "ghc")* would normally give you the path to GHC.The path returned by J name7 corresponds to the program that would be executed by  $ when passed the same string (as a  RawCommand, not a  ShellCommand), provided that name4 is not a relative path with more than one segment. On Windows, J calls the Win32 function  6https://msdn.microsoft.com/en-us/library/aa365527.aspx SearchPathH, which may search other places before checking the directories in the PATH environment variable. Where it actually searches depends on registry settings, but notably includes the directory containing the current executable.8On non-Windows platforms, the behavior is equivalent to O( using the search directories from the PATHx environment variable and testing each file for executable permissions. Details can be found in the documentation of O.K]Search for executable files in a list of system-defined locations, which generally includes PATH and possibly more.On Windows, this  only returns the first ocurrence4, if any. Its behavior is therefore equivalent to J.9On non-Windows platforms, the behavior is equivalent to L' using the search directories from the PATHG environment variable. Details can be found in the documentation of L.Get the contents of the PATH environment variable.LGiven a name or path, J appends the Qv to the query and searches for executable files in the list of given search directories and returns all occurrences.The behavior is equivalent to O using the given search directories and testing each file for executable permissions. Details can be found in the documentation of O.(Unlike other similarly named functions, L does not use  SearchPathz from the Win32 API. The behavior of this function on Windows is therefore equivalent to those on non-Windows platforms./Test whether a file has executable permissions.M@Search through the given list of directories for the given file.The behavior is equivalent to OV, returning only the first occurrence. Details can be found in the documentation of O.NsSearch through the given list of directories for the given file and returns all paths where the given file exists.The behavior is equivalent to P1. Details can be found in the documentation of P.OSearch through a given list of directories for a file that has the given name and satisfies the given predicate and return the path of the first occurrence. The directories are checked in a left-to-right order.1This is essentially a more performant version of P_ that always returns the first result, if any. Details can be found in the documentation of P.P!findFilesWith predicate dirs name, searches through the list of directories (dirs ) for files that have the given name and satisfy the given  predicate ands return the paths of those files. The directories are checked in a left-to-right order and the paths are returned in the same order.If the name5 is a relative path, then for every search directory dir, the function checks whether dir  name. exists and satisfies the predicate. If so, dir  name is returned as one of the results. In other words, the returned paths can be either relative or absolute depending on the search directories were used. If there are no search directories, no results are ever returned.If the name is an absolute path, then the function will return a single result if the file exists and satisfies the predicate and no results otherwise. This is irrespective of what search directories were given.QOFilename extension for executable files (including the dot if any) (usually "" on POSIX systems and ".exe" on Windows or OS/2).R Similar to S+, but always includes the special entries (. and ..&). (This applies to Windows as well.)3The operation may fail with the same exceptions as S.SS dir returns a list of all entries in dir without the special entries (. and ..).The operation may fail with: HardwareFault* A physical I/O error has occurred. [EIO]InvalidArgument2 The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]E /  NoSuchThing% The directory does not exist. [ENOENT, ENOTDIR]C / PermissionDeniedI The process has insufficient privileges to perform the operation. [EACCES]ResourceExhaustedF Insufficient resources are available to perform the operation. [EMFILE, ENFILE]e< The path refers to an existing non-directory object.  [ENOTDIR]T/Change the working directory to the given path. In a multithreaded program, the current working directory is a global state shared among all threads of the process. Therefore, when performing filesystem operations from multiple threads, it is highly recommended to use absolute rather than relative paths (see: H).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument. The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]E or  NoSuchThing! The directory does not exist. [ENOENT, ENOTDIR]C or PermissionDeniedE The process has insufficient privileges to perform the operation. [EACCES]f{ The operating system has no notion of current working directory, or the working directory cannot be dynamically changed.e8 The path refers to an existing non-directory object.  [ENOTDIR]URun an  action with the given working directory and restore the original working directory afterwards, even if the given action fails due to an exception.3The operation may fail with the same exceptions as  and T.V#Obtain the size of a file in bytes.WTest whether the given path points to an existing filesystem object. If the user lacks necessary permissions to search the parent directories, this function may return false even if the file does actually exist.XThe operation X returns ^ if the argument file exists and is either a directory or a symbolic link to a directory, and  otherwise.YThe operation Y returns 9 if the argument file exists and is not a directory, and  otherwise.Z Create a file symbolic link. The target path can be either absolute or relative and need not refer to an existing file. The order of arguments follows the POSIX convention..To remove an existing file symbolic link, use A.!Although the distinction between file symbolic links and  directory symbolic links does not exist on POSIX systems, on Windows this is an intrinsic property of every symbolic link and cannot be changed without recreating the link. A file symbolic link that actually points to a directory will fail to dereference and vice versa. Moreover, creating symbolic links on Windows requires privileges normally unavailable to users outside the Administrators group. Portable programs that use symbolic links should take both into consideration..On Windows, the function is implemented using CreateSymbolicLink with dwFlags+ set to zero. On POSIX, the function uses symlink and is therefore atomic.6Windows-specific errors: This operation may fail with AU if the user lacks the privileges to create symbolic links. It may also fail with B5 if the file system does not support symbolic links.[ Create a  directory symbolic link. The target path can be either absolute or relative and need not refer to an existing directory. The order of arguments follows the POSIX convention.3To remove an existing directory symbolic link, use \.!Although the distinction between file symbolic links and  directory symbolic links does not exist on POSIX systems, on Windows this is an intrinsic property of every symbolic link and cannot be changed without recreating the link. A file symbolic link that actually points to a directory will fail to dereference and vice versa. Moreover, creating symbolic links on Windows requires privileges normally unavailable to users outside the Administrators group. Portable programs that use symbolic links should take both into consideration..On Windows, the function is implemented using CreateSymbolicLink with dwFlags set to SYMBOLIC_LINK_FLAG_DIRECTORY#. On POSIX, this is an alias for Z and is therefore atomic.6Windows-specific errors: This operation may fail with AU if the user lacks the privileges to create symbolic links. It may also fail with B5 if the file system does not support symbolic links.\Remove an existing  directory symbolic link.!On Windows, this is an alias for >+. On POSIX systems, this is an alias for A. See also: A, which can remove an existing file symbolic link.]yCheck whether the path refers to a symbolic link. An exception is thrown if the path does not exist or is inaccessible.On Windows, this checks for FILE_ATTRIBUTE_REPARSE_POINTz. In addition to symbolic links, the function also returns true on junction points. On POSIX systems, this checks for S_IFLNK._Retrieve the target path of either a file or directory symbolic link. The returned path may not be absolute, may not exist, and may not even be a valid path.On Windows systems, this calls DeviceIoControl with FSCTL_GET_REPARSE_POINTm. In addition to symbolic links, the function also works on junction points. On POSIX systems, this calls readlink.7Windows-specific errors: This operation may fail with B5 if the file system does not support symbolic links.`AObtain the time at which the file or directory was last accessed.The operation may fail with:C< if the user is not permitted to read the access time; orE) if the file or directory does not exist.Caveat for POSIX systems: This function returns a timestamp with sub-second resolution only if this package is compiled against  unix-2.6.0.07 or later and the underlying filesystem supports them.aAObtain the time at which the file or directory was last modified.The operation may fail with:CB if the user is not permitted to read the modification time; orE) if the file or directory does not exist.Caveat for POSIX systems: This function returns a timestamp with sub-second resolution only if this package is compiled against  unix-2.6.0.07 or later and the underlying filesystem supports them.bAChange the time at which the file or directory was last accessed.The operation may fail with:C= if the user is not permitted to alter the access time; orE) if the file or directory does not exist.Some caveats for POSIX systems:Not all systems support  utimensat, in which case the function can only emulate the behavior by reading the modification time and then setting both the access and modification times together. On systems where  utimensatN is supported, the access time is set atomically with nanosecond precision.!If compiled against a version of unix prior to 2.7.0.0, the function would not be able to set timestamps with sub-second resolution. In this case, there would also be loss of precision in the modification time.cAChange the time at which the file or directory was last modified.The operation may fail with:CC if the user is not permitted to alter the modification time; orE) if the file or directory does not exist.Some caveats for POSIX systems:Not all systems support  utimensat, in which case the function can only emulate the behavior by reading the access time and then setting both the access and modification times together. On systems where  utimensatW is supported, the modification time is set atomically with nanosecond precision.!If compiled against a version of unix prior to 2.7.0.0, the function would not be able to set timestamps with sub-second resolution. In this case, there would also be loss of precision in the access time.d*Returns the current user's home directory.The directory returned is expected to be writable by the current user, but note that it isn't generally considered good practice to store application-specific data here; use e or g instead. On Unix, d returns the value of the HOMEg environment variable. On Windows, the system is queried for a suitable path; a typical path might be  C:/Users/<user>.The operation may fail with:f6 The operating system has no notion of home directory.EL The home directory for the current user does not exist, or cannot be found.eObtain the paths to special directories for storing user-specific application data, configuration, and cache files, conforming to the  Fhttp://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification. Compared with gf, this function provides a more fine-grained hierarchy as well as greater flexibility for the user.0It also works on Windows, although in that case 1 and 2# will map to the same directory.The second argument is usually the name of the application. Since it will be integrated into the path, it must consist of valid path characters.hNote: The directory may not actually exist, in which case you would need to create it with file mode 700% (i.e. only accessible by the owner).0Return the value of an environment variable, or  J if there is no such value. (Equivalent to "lookupEnv" from base-4.6.)gObtain the path to a special directory for storing user-specific application data (traditional Unix location). Newer applications may prefer the the XDG-conformant location provided by e ( Chttps://github.com/haskell/directory/issues/6#issuecomment-96521020migration guide).The argument is usually the name of the application. Since it will be integrated into the path, it must consist of valid path characters."On Unix-like systems, the path is ~/.<app>.On Windows, the path is  %APPDATA%/<app> (e.g.  C:/Users/<user>/AppData/Roaming/<app>)Note: the directory may not actually exist, in which case you would need to create it. It is expected that the parent directory exists and is writable.The operation may fail with:fU The operating system has no notion of application-specific data directory.EV The home directory for the current user does not exist, or cannot be found.h.Returns the current user's document directory.The directory returned is expected to be writable by the current user, but note that it isn't generally considered good practice to store application-specific data here; use e or g instead. On Unix, h returns the value of the HOMEg environment variable. On Windows, the system is queried for a suitable path; a typical path might be  C:/Users/<user> /Documents.The operation may fail with:f: The operating system has no notion of document directory.EP The document directory for the current user does not exist, or cannot be found.i2Returns the current directory for temporary files. On Unix, i returns the value of the TMPDIR environment variable or "/tmp" if the variable isn't defined. On Windows, the function checks for the existence of environment variables in the following order and uses the first path found:TMP environment variable.TEMP environment variable.!USERPROFILE environment variable.The Windows directoryThe operation may fail with:f; The operating system has no notion of temporary directory.4The function doesn't verify whether the path exists.=Create its parents too?*The path to the directory you want to makeDOld pathNew pathESource filenameDestination filenameSource filenameDestination filenameSource filenameDestination filename Post-actionDestination file Post-action Main action Source fileDestination handle Source handleDestination handleF Source fileDestination fileUDirectory to execute inAction to be executedZpath to the target filepath of the link to be created[path to the target directorypath of the link to be createdewhich special directoryWa relative path that is appended to the path; if empty, the base path is returnedfwhich special directory listg/a relative path that is appended to the pathC-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiG<=>?@BSRTUd0123e-./fghiACDEFVGHIWYXJKLMNOPQZ[\]_456789:;`abc^-./0123 Safe4y     !"#$%&'()*+,-./01123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Z      !"#$%&'()*+,-./012131456789:;<=>=?@ABCBDBEBFGHIJKLMNOPQRSTUVWXYZ[\]\^\_\`abacadaeafagahaiajakalamanaoapaqrsrtrurvrwxyxz{|}~}}}XZ1//      !"#$%&%'%()*+,-./012345678978:;78<=>78?@.A(directory-1.3.2.1-BeY7EsbU2McEERsEtHRAv3System.Directory.InternalSystem.Directory System.Directory.Internal.Config!System.Directory.Internal.Prelude System.Directory.Internal.CommonSystem.Directory.Internal.Posix%System.Directory.Internal.C_utimensatSystem.Process createProcess!System.Directory.Internal.Windows Permissionsreadablewritable executable searchableFileTypeFile SymbolicLink Directory DirectoryLinktryIOErrorTypespecializeErrorStringioeAddLocationfileTypeIsDirectorygetCurrentDirectoryprependCurrentDirectoryModeMetadata c_realpathc_free c_PATH_MAX withRealpathgetSymbolicLinkMetadatagetFileMetadatafileTypeFromMetadatafileSizeFromMetadataaccessTimeFromMetadatamodificationTimeFromMetadataposix_accessTimeHiResposix_modificationTimeHiResmodeFromMetadata allWriteMode hasWriteMode setWriteMode setFileModesetFilePermissionsgetAccessPermissionssetAccessPermissions CTimeSpec c_utimensat c_AT_FDCWD utimeOmit toCTimeSpecXdgDirectoryList XdgDataDirs XdgConfigDirs XdgDirectoryXdgData XdgConfigXdgCacheemptyPermissionssetOwnerReadablesetOwnerWritablesetOwnerExecutablesetOwnerSearchablegetPermissionssetPermissionscopyPermissionscreateDirectorycreateDirectoryIfMissingremoveDirectoryremoveDirectoryRecursiveremovePathForcibly removeFilerenameDirectory renameFile renamePathcopyFilecopyFileWithMetadatacanonicalizePath makeAbsolutemakeRelativeToCurrentDirectoryfindExecutablefindExecutablesfindExecutablesInDirectoriesfindFile findFiles findFileWith findFilesWith exeExtensiongetDirectoryContents listDirectorysetCurrentDirectorywithCurrentDirectory getFileSize doesPathExistdoesDirectoryExist doesFileExistcreateFileLinkcreateDirectoryLinkremoveDirectoryLinkpathIsSymbolicLinkisSymbolicLinkgetSymbolicLinkTarget getAccessTimegetModificationTime setAccessTimesetModificationTimegetHomeDirectorygetXdgDirectorygetXdgDirectoryListgetAppUserDataDirectorygetUserDocumentsDirectorygetTemporaryDirectory$fBoundedXdgDirectory$fEnumXdgDirectory$fEqXdgDirectory$fOrdXdgDirectory$fReadXdgDirectory$fShowXdgDirectory$fBoundedXdgDirectoryList$fEnumXdgDirectoryList$fEqXdgDirectoryList$fOrdXdgDirectoryList$fReadXdgDirectoryList$fShowXdgDirectoryListbaseGHC.Base++ghc-primGHC.PrimseqGHC.Listfilterzip System.IOprint Data.Tuplefstsnd otherwisemap$GHC.Real fromIntegral realToFracGHC.EnumBoundedminBoundmaxBoundEnumenumFrom enumFromThenenumFromThenTo enumFromTofromEnumtoEnumsuccpred GHC.ClassesEq==/= GHC.FloatFloatingpiexplogsqrt**logBasesincostanasinacosatansinhcoshtanhasinhacoshatanh Fractional fromRational/recipIntegral toIntegerquotremdivmodquotRemdivModMonad>>=>>returnfailFunctorfmap<$GHC.NumNum*+-negate fromIntegerabssignumOrd>=minmax><<=compareGHC.ReadRead readsPrecreadListReal toRational RealFloat floatRadix floatDigits floatRange decodeFloat encodeFloatexponent significand scaleFloatisNaN isInfiniteisDenormalizedisNegativeZeroisIEEEatan2RealFracproperFractiontruncateroundceilingfloorGHC.ShowShow showsPrecshowshowList Applicativepure<*>*><* Data.FoldableFoldablefoldrfoldMapnulllengthfoldlfoldl1sumproductfoldr1maximumminimumelemData.Traversable TraversabletraversemapM sequenceAsequenceMonoidmemptymappendmconcat GHC.TypesBoolFalseTrueCharDoubleFloatInt integer-gmpGHC.Integer.TypeIntegerMaybeNothingJustOrderingLTEQGTRationalIOWordGHC.PtrPtr Data.EitherEitherLeftRightGHC.IO.Handle.TypesHandleSystem.Posix.Internals withFilePath Data.VoidVoidSystem.TimeouttimeoutSystem.EnvironmentgetEnvgetArgs System.Exit exitFailure Control.Monadunless replicateM_<=<>=>for Control.ArrowsecondopenBinaryTempFilewithBinaryFilereadIOreadLn appendFile writeFilereadFileinteract getContentsgetLinegetCharputStrLnputStrputChar GHC.IO.HandlehCloseGHC.IO.Handle.FDstderrGHC.IO.Handle.TexthGetBufhPutBuf hPutStrLnhPutStrSystem.IO.Error catchIOError modifyIOErrorioeSetFileNameioeSetLocationioeSetErrorStringioeGetLocationioeGetErrorStringioeGetErrorTypepermissionErrorTypeillegalOperationErrorTypeisPermissionErrorisIllegalOperationisDoesNotExistErrorisAlreadyExistsError mkIOError tryIOErrorControl.Exception.Basebracket_finallybracket onExceptiontry GHC.Conc.Sync killThreadforkIOSystem.Posix.Types EpochTimeForeign.C.ErrorthrowErrnoPathIfMinus1_throwErrnoIfNullthrowErrnoIfMinus1Retry_throwErrnoIfMinus1_Foreign.C.String withCWStringpeekCWStringLen withCString peekCStringCStringCWStringForeign.Marshal.Array withArray allocaArrayForeign.Marshal.Utils maybeWithwithForeign.Marshal.AllocallocaBytesAligned allocaBytesallocaGHC.IO.ExceptionioError IOErrorType OtherErrorInappropriateTypeUnsupportedOperationhFlushstdoutGHC.IO.EncodinggetFileSystemEncoding GHC.IORef writeIORef readIORefnewIORefIORefGHC.IOmaskthrowIOcatchFilePath userErrorIOErrornotElemallanyorand concatMapconcat sequence_mapM_for_ traverse_ Data.Monoid<> Data.OldListunwordswordsunlineslines Text.ReadreadreadseitherForeign.C.TypesCUCharCUShortCIntCLongCULongCWcharCTime GHC.IO.IOModeIOModeReadMode WriteModeForeign.StorableStorablesizeOf alignment peekElemOff pokeElemOff peekByteOff pokeByteOffpeekpokeplusPtrnullPtrlex readParenText.ParserCombinators.ReadPReadS GHC.UnicodetoUppertoLowerisAlphaisAscii Data.Bits.&..|. complement Data.Functionon Data.Functor<$>lcmgcd^^^oddeven showParen showStringshowCharshowsShowSunzip3unzipzipWith3zipWithzip3!!lookupreversebreakspansplitAtdroptake dropWhile takeWhilecycle replicaterepeatiteratescanr1scanrscanl1scanlinitlasttailhead Data.Maybe catMaybes maybeToList fromMaybemaybeuncurrycurryGHC.MVarputMVarreadMVartakeMVar newEmptyMVarsubtractasTypeOfuntil$!flip.constidwhen=<<StringGHC.Err undefinederrorWithoutStackTraceerror GHC.Exception SomeException&&||notListTremovePathRecursiveremoveContentsRecursivecopyFileContentsatomicCopyFileContentswithReplacementFileignoreIOExceptionscopyFileToHandlecopyHandleDatafilepath-1.4.1.2System.FilePath.Posix normalisedropTrailingPathSeparatormatchTrailingSeparator makeRelativegetPath isExecutable lookupEnv