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

Unable to write to dirty settings file #19161

Closed
isidorn opened this issue Jan 24, 2017 · 7 comments
Closed

Unable to write to dirty settings file #19161

isidorn opened this issue Jan 24, 2017 · 7 comments
Assignees
Labels
settings-editor VS Code settings editor issues verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Jan 24, 2017

Now we have more and more menu actions that write immediatly to settings, for instance toggle word wrap.
If you have a dirty settings.json all these actions are broken as I always get the erros that I am unable to write to a dirty settings file

I believe this can hurt a lot of our users as they usualy do not have auto save on, and showing an error message in this case looks bad imho.

screen shot 2017-01-24 at 12 26 32

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Jan 24, 2017
@sandy081 sandy081 added this to the February 2017 milestone Jan 24, 2017
@sandy081 sandy081 added config VS Code configuration, set up issues workbench labels Jan 24, 2017
@sandy081 sandy081 added feature-request Request for new features or functionality and removed bug Issue identified by VS Code Team member as probable bug labels Feb 1, 2017
@sandy081
Copy link
Member

sandy081 commented Feb 1, 2017

Related to #19625

@sandy081
Copy link
Member

sandy081 commented Feb 2, 2017

We can write into the opened buffer but saving the file automatically might be problematic. Because user might have changes which he does not want to save.

One approach is to inform user about saving the Settings for the action to take affect
Or to enable auto save for the settings always

@sandy081 sandy081 modified the milestones: Backlog, February 2017 Feb 2, 2017
@isidorn
Copy link
Contributor Author

isidorn commented Feb 2, 2017

Enable auto save for settings, my suggestion :)

@sandy081 sandy081 added settings-editor VS Code settings editor issues and removed config VS Code configuration, set up issues feature-request Request for new features or functionality labels May 12, 2017
@sandy081 sandy081 modified the milestones: May 2017, Backlog May 15, 2017
@sandy081
Copy link
Member

Provided an option to save and retry settings in this case. This is a good compromise and helps users to quickly fix it.

image

@sandy081 sandy081 added the verification-needed Verification of issue is requested label May 15, 2017
sandy081 added a commit that referenced this issue May 15, 2017
marckassay pushed a commit to marckassay/vscode that referenced this issue May 15, 2017
@isidorn
Copy link
Contributor Author

isidorn commented May 30, 2017

@sandy081 I get a nice error dialog to open settings, however I do not get the option to save and retry.
I am trying with user settings, latest insider

@sandy081
Copy link
Member

@isidorn Please try when the file is dirty without any errors. If there are errors, then I show a message to open and fix errors.

@isidorn isidorn added the verified Verification succeeded label May 31, 2017
@lynochka
Copy link

Hei, similary, would not allow to rewrite because of diry file {
"terminal.integrated.shell.windows": "C:\Windows\System32\cmd.exe"
}

please help

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
settings-editor VS Code settings editor issues verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants