Jean-Francois LARVOIRE

This is still the case with Windows 10 and 11.

I agree with this patch. It's sorely needed!

There is no 260 character limit on Windows. There was indeed one in Windows 95 due to FAT32 limitations. But ever since NT4 with NTFS (That's 20 years ago!), Windows supports at least 64KB paths. Their real mistake was to invent that awful \\?\ trick for unlocking the new capability, presumably to prevent a buffer overflow in one of their old applications. The real fix is not to try using the \\?\ prefix in your program. Instead, the real fix would be to silently insert that prefix inside mingw file...

There is no 260 character limit on Windows. There was indeed one in Windows 95 due to FAT32 limitations. But ever since NT4 with NTFS (That's 20 years ago!), Windows supports at least 64KB paths. Their real mistake was to invent that awful \\?\ trick for unlocking the new capability, presumably to prevent buffer overlow in one of their old applications. The real fix is not to try using the \\?\ prefix in your program. Instead, the real fix would be to silently insert that prefix inside mingw file...

There is no 260 character limit on Windows. There was indeed one in Windows 95 due to FAT32 limitations. But ever since NT4 with NTFS (That's 20 years ago!), Windows supports at least 64KB paths. Their real mistake was to invent that awful \\?\ trick, presumably to prevent buffer overlow in one of their old applications. The real fix is not to try using the \\?\ prefix in your program. Instead, the real fix would be to silently insert that prefix inside mingw file I/O libraries. This way, every time...

There is no 260 character limit on Windows. There was indeed one in Windows 95 due to FAT32 limitations. But ever since NT4 with NTFS (That's 20 years ago!), Windows supports at least 64KB paths. The real fix is not to try using the \?\ prefix in your program. Instead, the real fix would be to silently insert that prefix inside mingw file I/O libraries. This way, every time a program opens a file the standard way, it just works, whatever the pathname length. I've done that in my MSVC Library eXtension,...

The default installation directory should certainly remain in " C:\Program Files\jEdit"....

I agree that this is confusing, and not just in jEdit: All Windows applications that...