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

go to definition to modules opens file in a wrong case on Windows #56

Open
nadako opened this issue Sep 6, 2016 · 4 comments
Open

go to definition to modules opens file in a wrong case on Windows #56

nadako opened this issue Sep 6, 2016 · 4 comments

Comments

@nadako
Copy link

nadako commented Sep 6, 2016

Look at how it opens DisplayTypes.ml tab, even though the file defining this module is called displayTypes.ml:

I think this actually makes VSCode go crazy and display duplicate search results if we have an open file in the different cache, like this:

@hackwaly
Copy link
Owner

hackwaly commented Sep 7, 2016

I didn't change the case in extension, seems merlin did it. It's difficult to restore it, and easy to solve it in VS Code side (detect platform is Windows and respect case insensitive).

@nadako
Copy link
Author

nadako commented Sep 7, 2016

I see. Well, I reported the issue to vscode too.

@hackwaly
Copy link
Owner

Maybe better report this to merlin.

I found https://www.npmjs.com/package/true-case-path. I'm trying to solve it at extension side, however it may cause performance issue.

@Simn
Copy link

Simn commented Apr 22, 2017

This is driving me crazy because I constantly end up having various open files duplicated. Is there any way we can work around the issue?

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

No branches or pull requests

3 participants