-
-
Notifications
You must be signed in to change notification settings - Fork 35
Using formatter findent with format code on save produces error "Failed to save" file #364
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
Comments
Yeah, we have not implemented |
Bumping up this issue - at least some error-handling, as this is a very annoying and confusing error to get if you have |
Does setting up the formatter to "Disabled" for the extension solve the issue? |
if you mean setting |
No, I mean the extension's settings for formatting: |
Hi, I had similar issue today. the issue is still there ! as additional info, I am using:
|
Thanks @HamGhibli that's what I wanted to know. BTW are you sure that version I am slightly short on time so any volunteers for this would be appreciated. |
Hey guys I implemented a potential fix here: #370. Please let me know how it is |
@gnikit thanks for the reply. I did not switch to the pre-release version yet... |
This is a proper async implementation of the formatting interface for simple edits. It can be extended to ranges as well, with minimal code. Closes Using formatter findent with format code on save produces error "Failed to save" file #364
I have issued a fix as a pre-release, I would NOTE the different interface that we have adopted in the extension. |
Describe the bug
When using the formatter findent with option
"editor.formatOnSave": true
, every time I got the following error message:I do not get this error when using formatter fprettify which is very slow in compare to findent.
To Reproduce
Steps to reproduce the behavior:
file.f90
Expected behavior
Saved formatted file.
Build info (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: