3 ms·

> I also hate that Windows paths are limited to 260 characters !? Easily changed in the registry/ with group policy, though 256 should not be the default today

• mkoubaa 2y ago
  Can you assume your users do that?
  • smegsicle 2y ago
    if they installed windows they knew exactly what they were signing up for
• jonathanlydall 2y ago
  Was going to say the situation with path lengths on Windows is mostly gone today, but it does still pop up on the odd occasion. For example the built in .zip file support can’t extract long paths (7-zip however has no issue). Also my Git client of choice (TortoiseGit) doesn’t fully handle long paths. But day to day long paths on Windows is fortunately not really an issue any more and they’ve been steadily improving support over the years. Despite generally being a fan of Windows, before Windows 10 the long path situation was infuriating, they even had a blog post acknowledging it’s a problem, but also stating it was going to be very non trivial to fix and as such they didn’t have any particular plans to fix it. I suspect that WSL made the limitation more regularly painful enough that they could convince managers that it’s something that had to get fixed. Windows Terminal was probably also motivated by WSL.
• nullindividual 2y ago
  MAX_PATH used to be 260 characters but was changed fairly early in Windows 10 life to 32k. NTFS has always supported 32k characters in the path with each part being no more than 255 characters. Office, OTOH, does not respect/observe MAX_PATH. Do not exceed ~240 characters in the path + filename for an Office document as Office will be unable to open it.