You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode first copies the file to reformat into a temporary .py..tmp file, then calls Black on that file, and brings the changes in the modified files back into the editor. This happens in the same location as the existing file.
We have processes that are notified of file creation, deletion, and changes; so this is causing some churn as it's catching the creation and deletion of the tmp file. Would it be possible to add an option to change the location of these tmp files to somewhere like /tmp? Or not even use a tmp file if it's not strictly necessary.
The text was updated successfully, but these errors were encountered:
There is better solution. We plan on putting formatting behind Language Server protocol. A benefit of that is we won't need temp files to perform formatting.
@jadami10 Currently we are working on getting linters over LSP #17235. I just created this meta issue to track the transition of formatters to LSP #17918.
VSCode first copies the file to reformat into a temporary .py..tmp file, then calls Black on that file, and brings the changes in the modified files back into the editor. This happens in the same location as the existing file.
We have processes that are notified of file creation, deletion, and changes; so this is causing some churn as it's catching the creation and deletion of the tmp file. Would it be possible to add an option to change the location of these tmp files to somewhere like
/tmp
? Or not even use a tmp file if it's not strictly necessary.The text was updated successfully, but these errors were encountered: