Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Win10 long paths support - inquiry #4078

Open
CookiePLMonster opened this issue Jan 12, 2018 · 1 comment
Open

Win10 long paths support - inquiry #4078

CookiePLMonster opened this issue Jan 12, 2018 · 1 comment

Comments

@CookiePLMonster
Copy link
Contributor

CookiePLMonster commented Jan 12, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants