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

fix: normalize paths before comparing equality #513

Closed
wants to merge 1 commit into from
Closed

fix: normalize paths before comparing equality #513

wants to merge 1 commit into from

Conversation

replicaJunction
Copy link
Contributor

Fix consistency issues on Windows when some linters use a single backslash, some use a double (escaped) backslash, and some still use a forward slash.

This fix is confirmed to fix issues with Mypy on Windows, and it probably affects other linters as well.

Fixes #480.

@replicaJunction
Copy link
Contributor Author

Although this is a small change, it makes a big difference in usability for me. Is there anything I can do to get this ready for review?

Fix consistency issues on Windows when some linters use a single
backslash, some use a double (escaped) backslash, and some still use a
forward slash.

This fix is confirmed to fix issues with Mypy on Windows, and it
probably affects other linters as well.

Fixes #480.
@mfussenegger
Copy link
Owner

Thanks. Added a small fixup to maintain compatibility with older neovim versions and merged via #539

For the future please use a feature branch. I cannot ammend to PRs created from master.

@replicaJunction
Copy link
Contributor Author

Understood. I apologize - I thought forking the repo counted my master as being a feature.

I appreciate you looking at this and merging the fix. Thank you!

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

Successfully merging this pull request may close these issues.

Backslash in the Windows path causes missing error report
2 participants