We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I changed "Supported File Formats" to: .cpp; .c; .h; .hpp; .cs; .js; .vb; .txt;*.sh;*.py
.cpp; .c; .h; .hpp; .cs; .js; .vb; .txt;*.sh;*.py
However, if I right click on a Python file, and try to unify the line endings, it says:
If I rename the .py file to an otherwise supported file, i.e. .cpp, and try to unify the line endings, it works fine.
Honestly - these are all text files, it's frustrating to have it enforce file safety.
I also tried putting the *.py extension at the start of the "Supported File Formats" but that didn't do anything either.
All other options were default.
The text was updated successfully, but these errors were encountered:
I also tried ".". It didn't allow any line endings to be unified.
Any updates? Otherwise, this is super useful.
Sorry, something went wrong.
No branches or pull requests
I changed "Supported File Formats" to:
.cpp; .c; .h; .hpp; .cs; .js; .vb; .txt;*.sh;*.py
However, if I right click on a Python file, and try to unify the line endings, it says:
If I rename the .py file to an otherwise supported file, i.e. .cpp, and try to unify the line endings, it works fine.
Honestly - these are all text files, it's frustrating to have it enforce file safety.
I also tried putting the *.py extension at the start of the "Supported File Formats" but that didn't do anything either.
All other options were default.
The text was updated successfully, but these errors were encountered: