-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Auto save behaviour might be unexpected here #141473
Comments
@lramos15 do you know if there's a way to disable autosave on a per-editor basis? |
There is currently none that I'm aware of. @bpasero would know more. Maybe we want to explore more granular configuration for that. Although what's the issue with autosave here exactly is it that if you're editing memory and it saves prematurely it may mess things up? |
No, see #42170. It is not so trivial to do per editor/folder but maybe I could revisit that. |
This is also something I wished I had working on the onedrive browser prototype (which is likely to be published eventually) since saving files to OneDrive is not very fast and creates "revisions" which can be confusing if numerous. |
@bpasero Please do as this would be very beneficial. An example use case, and the reason I searched for this, is I currently have several VS Code instances open. One for an Angular project that drives our frontend and one for our AWS/API that drives our backend. I want the autosave feature enabled for the AWS/API project because I don't want to miss any changes during a deployment (you get used to the autosave feature and forgot to save at times). However, the Angular project is pretty large and it takes a while to rebuild when using the live development server. If the autosave feature is on, then it will constantly keep trying to rebuild on every autosave. So, I leave the autosave feature off and when I'm ready to test changes I just use the save all (CTRL+K S) shortcut keys. Then it only does it once. I have to remember that if I turn off the autosave on the Angular project, then it turns it off for the AWS/API project as well. So, enabling and disabling the autosave feature affects all instances of VS Code open. |
@connor4312 auto save can be configured per resource and/or editor since a few milestones and we use this already to disable auto save when AI suggestions are made. See along this method: vscode/src/vs/workbench/services/filesConfiguration/common/filesConfigurationService.ts Line 95 in 676cbd9
|
Testing #141347
I have auto save enabled. This makes sense when editing files, but feels different when editing memory during debugging.
The text was updated successfully, but these errors were encountered: