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
Are there any immediate or long term plans to support Windows 10 long paths? As stated by MSDN:
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.
While long paths existed for a long time, using them in code meant opting out of path canonization which sometimes is undesirable. With Win10 long paths, looks like this is not the case anymore and the limit has been lifted without any compromises.
What it means for Notepad++ is that when all instances of MAX_PATH are gone from the code (looks like there are a lot of places where this constant is relied upon) a manifest flag can be switched and it can begin using long paths on systems where they are available, without compromising compatibility with older systems.
This might be way too complex for a single pull request with a single/a few commits - thus are there any plans to start development of a rework like this eg. in a branch?
EDIT:
For the record, vscode seems to work "fine" with long paths. I just confirmed n++ doesn't.
The text was updated successfully, but these errors were encountered:
Are there any immediate or long term plans to support Windows 10 long paths? As stated by MSDN:
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.
While long paths existed for a long time, using them in code meant opting out of path canonization which sometimes is undesirable. With Win10 long paths, looks like this is not the case anymore and the limit has been lifted without any compromises.
What it means for Notepad++ is that when all instances of
MAX_PATH
are gone from the code (looks like there are a lot of places where this constant is relied upon) a manifest flag can be switched and it can begin using long paths on systems where they are available, without compromising compatibility with older systems.This might be way too complex for a single pull request with a single/a few commits - thus are there any plans to start development of a rework like this eg. in a branch?
EDIT:
For the record, vscode seems to work "fine" with long paths. I just confirmed n++ doesn't.
The text was updated successfully, but these errors were encountered: