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 Sublime's expand_variables for UNC paths #1597

Merged
merged 1 commit into from
Apr 25, 2019
Merged

Conversation

kaste
Copy link
Contributor

@kaste kaste commented Apr 24, 2019

Fixes SublimeLinter/SublimeLinter-eslint#276

Explainer and origin: sublimehq/sublime_text#1878

Sublime's expand_variables handles \\ (two slashes) and reduces them to one. We fix by adding more slashes before substituting.

Fixes SublimeLinter/SublimeLinter-eslint#276

Explainer and origin: sublimehq/sublime_text#1878

Sublime's `expand_variables` handles `\\` (two slashes) and reduces them to one.
We fix by adding more slashes before substituting.
@braver
Copy link
Member

braver commented Apr 24, 2019

Wow, why is "Textmate compatibility" still a thing? 🚢 it, it's not like I can test this right?

@kaste kaste merged commit 1248915 into master Apr 25, 2019
@kaste
Copy link
Contributor Author

kaste commented Apr 25, 2019

The current PR's are all hard to test, I also have to mock my env, run fake linter plugins. It really pays off that we have tests now. We had basically zero issues with our latest releases.

@kaste kaste deleted the fixup-expand-variables branch April 25, 2019 12:33
@kaste kaste added this to the 4.11.1 milestone Apr 25, 2019
@kaste kaste added the bug label Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

UNC Paths Failing in New Version
2 participants