Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions.
In case long path behavior is enabled I would like suggest do not show warning about long path.
More info https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation
Remove warning about long path
Moderators: Hacker, petermad, Stefan2, white
Re: Remove warning about long path
Since TC is not long path aware, at least in regards to its (embedded) manifest, it can't just use the regular Win32 API functions without the long path prefix (\\?\). Furthermore, when copying files to an external drive, it's not a good idea to just skip the warning. Systems without this registry switch set won't be able to open long paths (outside of TC).
Regards
Dalai
PS: I'm still wondering why everyone, including developers, thinks that the MAX_PATH limit has been removed. It's an opt-in to remove it for select API functions, the system and the application must explicitely support it.
Regards
Dalai
PS: I'm still wondering why everyone, including developers, thinks that the MAX_PATH limit has been removed. It's an opt-in to remove it for select API functions, the system and the application must explicitely support it.
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Re: Remove warning about long path
To be more precise: Each application on the system should support this, if they want to access pathes with more than 259 characters.
This includes almost all of the TC-plugins and also shell extension which are normally not aware of long pathes and any program code using other WIN32-API methods than the short list of functions listed in the linked MS article.
It may be no big deal to enable this support for newer .net applications but a lot of work for programs using other frameworks. Not mention the fact that there are still a lot of older programs in use that are not actively developed anymore.
Removing this warning is imho a bad idea.
Regards
Holger
PS: (@Infector) If you know what you are doing and won't blame TC if your preferred Editor is unable to open a file in a long path;
there is a switch under windcmd.ini->[Configuration] to disable the warning:
LongNameCopy=0 During file operations, warn if target name is longer than 259 characters:
0=always
1=never
2=if source name isn't longer than 259 characters
3=disallow long names
Make our planet great again
Re: Remove warning about long path
@HolgerK thank you. I always forgot about hidden TC options.