getDirectoryContents
Similar to
listDirectory, but always includes the special
entries (
. and
..). (This applies to Windows as
well.)
The operation may fail with the same exceptions as
listDirectory.
Similar to
listDirectory, but always includes the special
entries (
. and
..). (This applies to Windows as
well.)
The operation may fail with the same exceptions as
listDirectory.
Get the contents of a directory. The result will be sorted, and will
not contain the entries
. or
.. (unlike the standard
Haskell version). The resulting paths will be relative to the first
argument. The result itself is tracked as a dependency, but the files
in the result are not. If the list of files changes in subsequent
builds any rule calling it will rerun.
It is usually simpler to call either
getDirectoryFiles or
getDirectoryDirs.
Retrieve the contents of a directory without any directory prefixes.
In contrast to
getDirectoryContents, exclude special
directories "." and "..".
Return the immediate children of a directory
Filters out "." and "..".
List all the files in a directory and all subdirectories.
The order places files in sub-directories after all the files in their
parent directories. The list is generated lazily so is not well
defined if the source directory structure changes before the list is
used.
Recursively list all the files and directories in a directory and all
subdirectories.
The directory structure is traversed depth-first.
The result is generated lazily so is not well defined if the source
directory structure changes before the list is fully consumed.
Symlinks within directory structure may cause result to be infinitely
long.
Get directory contents minus dot files.
Recursively list all the files and directories that satisfy given
predicate in a directory and all subdirectories. Descending into some
subdirectories may be avoided by filtering them out with a visiting
predicate.
Not visited directory entry may still be reported depending on the
collection predicate.
The directory structure is traversed depth-first.
The result is generated lazily so is not well defined if the source
directory structure changes before the list is fully consumed.
Symlinks within directory structure may cause result to be infinitely
long, but they can be filtered out with a suitable directory visiting
predicate.