I’m experiencing a persistent issue with the Cursor app. Whenever I save a file, the app gets stuck in an infinite loading state. Here are the error messages I’m receiving:
Error Messages:
• Saving ‘StudyMessageEdit.tsx’: Getting code actions from ‘TypeScript and JavaScript Language Features’, ‘cursor-retrieval’ (configure).
• Saving ‘settings.json’: Getting code actions from ‘JSON Language Features’, ‘cursor-retrieval’ (configure).
Has anyone encountered this problem before or have any insights on how to fix it? I’ve tried restarting the app and my computer, but the issue persists.
Any help or suggestions would be greatly appreciated!
I run into this from time to time as well. Its got something to do with the Format On Save setting under VSCode settings in cursor. Ironically when this happens and I try to turn off that setting it never saves the state so it remains on forcing me to copy my changed files into sublime close out cursor and then copy paste my updated files into cursor again and save. Really hope this gets looked into
I am sharing this same issue. Files cannot be saved if ESLint format on save or automatically adding missing imports is enabled. This makes it impossible to use Cursor
Same issue here. Cursor is stuck in “Saving ‘foo.cpp’ Writing into file…”
I tried everything, reboot, re-install, etc…
Weird thing is that if I change the file name I can finally save it, but if I change it back to its original name it won’t save… It currently only happens to me on a specific file, but it makes for some weird saving gymnastic.
When I apply changes from chat and the file auto-saves, I have to open the “Saving ‘MyComponent.vue’…” dialog, cancel save operation, select all, copy, close file in Cursor, open file in Vim, select all, paste, save there, then reopen in Cursor.
If you’re using the GitLens plugin, consider turning it off. When GitLens calculates Git Blame information, large recent commits can cause significant lag throughout VS Code. The plugin’s calculations for blame data can create bottlenecks that affect various VS Code operations, including ESLint processing.