You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tip: Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions. However, you must opt-in to the new behavior.
It's possible for all FS functions to use path lengths >260 characters now if the required registry key is set on Windows 10:
With this setting it's possible to create 32,767 long paths without using the specific Unicode Win32 API functions and the path prefix \\?\
Though still, each folder/file aka "component" name length cannot exceed 255 characters:
The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters).
#15
From MSDN:
It's possible for all FS functions to use path lengths >260 characters now if the required registry key is set on Windows 10:
HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled=1 (Type: REG_DWORD)
With this setting it's possible to create 32,767 long paths without using the specific Unicode Win32 API functions and the path prefix \\?\
Though still, each folder/file aka "component" name length cannot exceed 255 characters:
https://github.com/keplerproject/luafilesystem/blob/884b52a3b29661a10e183daf4cea7a37698f404b/src/lfs.c#L99 pattern length
https://github.com/keplerproject/luafilesystem/blob/884b52a3b29661a10e183daf4cea7a37698f404b/src/lfs.c#L186 get_dir function buffer size
https://github.com/keplerproject/luafilesystem/blob/884b52a3b29661a10e183daf4cea7a37698f404b/src/lfs.c#L555 dir_iter_factory: directory iterator
The text was updated successfully, but these errors were encountered: