I have Cursor and VS Code opened side-by-side. Each has the Black Formatter for python enabled to format on save.
When I save in VS Code the file saves rather quickly, applying all recommended formatting changes w/ Black.
When I save in Cursor the UI lags, the file does not save, and I get a toast stating “Saving : Running ‘Black Formatter’ Formatter” for ~30+ seconds before the file saves.
I’m having the same issue as the other users, hangs for 30+ seconds on saving. I need to switch back to vanilla VSCode to continue working. hope it’s fixed soon!
I have the same issue since monday, but weirdly I have it also in vscode. In the settings I have this part:
“[typescript]”: {
“editor.defaultFormatter”: “esbenp.prettier-vscode”,
“editor.codeActionsOnSave”: {
“source.organizeImports”: “explicit”,
“source.addMissingImports”: “explicit”,
“source.fixAll.eslint”: “explicit”
}
},
The file gets saved only, if I completely remove this section.
I also tried deactivating all extensions, but it did not work.
Still no go. I’ll delete the now-unused operator.enum.ts and comparison-type.enum.ts to see if that fixes the model’s caching problem. Starting with operator.enum.ts.
[…]
Last edit was wrong. recipients was removed; I’m adding it back.
[…]
It’s not working. I need to be more precise.
[…]
Tool’s failing. I’ll circle back. Now, dto/index.ts.
[…]
Tool’s broken. Moving on. Fixing recipients in e2e-test.factory.ts now.
[…]
Tool’s failing again. I need to give it more context.
[…]
I think it would be ideal if the Cursor IDE did NOT use “formatOnSave” for it’s agent, but instead used the built in VSCode setting “Save without formatting”.
Would be nice to find out from Cursor if this is already the case, and the “tool error” I am getting is related to something else: