Skip to content
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

Open
sbatten opened this issue Jan 25, 2022 · 6 comments
Open

Auto save behaviour might be unexpected here #141473

sbatten opened this issue Jan 25, 2022 · 6 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality polish Cleanup and polish issue
Milestone

Comments

@sbatten
Copy link
Member

sbatten commented Jan 25, 2022

Testing #141347

I have auto save enabled. This makes sense when editing files, but feels different when editing memory during debugging.

@connor4312
Copy link
Member

@lramos15 do you know if there's a way to disable autosave on a per-editor basis?

@connor4312 connor4312 added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality polish Cleanup and polish issue labels Jan 25, 2022
@connor4312 connor4312 added this to the On Deck milestone Jan 25, 2022
@lramos15
Copy link
Member

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?

@bpasero
Copy link
Member

bpasero commented Jan 26, 2022

No, see #42170. It is not so trivial to do per editor/folder but maybe I could revisit that.

@connor4312
Copy link
Member

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.

@JamesDougherty
Copy link

@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.

@bpasero
Copy link
Member

bpasero commented Aug 9, 2024

@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:

disableAutoSave(resourceOrEditor: EditorInput | URI): IDisposable;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality polish Cleanup and polish issue
Projects
None yet
Development

No branches or pull requests

5 participants