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

Allow to write to a file without permission after authentication #1779

Closed
HuanhuanSunMSFT opened this issue Jan 4, 2016 · 13 comments
Closed
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality workbench-run-as-admin Issues concerning running as administrator

Comments

@HuanhuanSunMSFT
Copy link

VS code on my Mac cannot save modified files suddenly. I tried restarting VS Code and MAC itself, but none brought saving back. It keeps popping this dialog when I cmd + S to save a file.

More information:
VS version: 0.10.6
vscode unable to save files 3
dev information 3

@joaomoreno joaomoreno added this to the Backlog milestone Jan 5, 2016
@bpasero
Copy link
Member

bpasero commented Jan 5, 2016

@HuanhuanSunMSFT did something change with your permissions? can you save with another editor?

@bpasero bpasero added the info-needed Issue requires more information from poster label Jan 5, 2016
@bpasero bpasero modified the milestones: Jan 2016, Backlog Jan 5, 2016
@HuanhuanSunMSFT
Copy link
Author

@bpasero I can save with Sublime 3. But I guess something permissions related did happen because when I save with Sublime 3, I need to input my password. However, I checked the file properties, it's not read only.

@bpasero
Copy link
Member

bpasero commented Jan 5, 2016

@HuanhuanSunMSFT this indicates that you are not the owner of the file and currently we do not support entering password during write.

@bpasero bpasero added feature-request Request for new features or functionality file-explorer Explorer widget issues and removed info-needed Issue requires more information from poster labels Jan 5, 2016
@bpasero bpasero changed the title Cannot save files on VS Code for MAC Allow to write to a file without permission after authentication Jan 5, 2016
@bpasero bpasero modified the milestones: Backlog, Jan 2016 Jan 5, 2016
@bpasero bpasero removed their assignment Jan 5, 2016
@HuanhuanSunMSFT
Copy link
Author

@bpasero that's interesting. How come I'm not the owner of this file? Though it may not be related to VS Code, how could I get into this state and get out of it?

@bpasero
Copy link
Member

bpasero commented Jan 5, 2016

I have no clue but this does not sound like something to discuss in the VSCode issue tracker.

@bpasero
Copy link
Member

bpasero commented Jan 5, 2016

rather StackOverflow 👍

@bpasero bpasero self-assigned this Mar 30, 2016
@bpasero bpasero removed their assignment Aug 17, 2016
@lukewhitehouse
Copy link

@bpasero Hey, just picking up on this one too. Is the idea of password prompts for saving files you don't have permission for on the roadmap for vscode? This was super useful when I used Sublime Text and I was editing /etc/hosts files, etc.

@isidorn
Copy link
Contributor

isidorn commented Nov 17, 2017

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!

@isidorn isidorn closed this as completed Nov 17, 2017
@lukewhitehouse
Copy link

lukewhitehouse commented Nov 17, 2017

@isidorn That's a shame but understand there are bigger fishes to fry. Is there anyway you can keep this tracked though, just closing the issue and pretending it doesn't exist disregards those of us who are looking to have this fixed?

If it's a current issue then this shouldn't be closed IMO.

@isidorn
Copy link
Contributor

isidorn commented Nov 17, 2017

Sure, we can reopen and put to backlog to keep track

@isidorn isidorn reopened this Nov 17, 2017
@isidorn isidorn added file-io File I/O and removed file-explorer Explorer widget issues labels Nov 17, 2017
@lukewhitehouse
Copy link

@isidorn Very much appreciated, thanks!

@bpasero bpasero added the workbench-run-as-admin Issues concerning running as administrator label Nov 18, 2017
@bpasero bpasero removed the file-io File I/O label Nov 18, 2017
@bpasero bpasero removed this from the Backlog milestone Nov 18, 2017
@bpasero
Copy link
Member

bpasero commented Dec 3, 2017

/duplicate of #1614

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 3, 2017
@vscodebot
Copy link

vscodebot bot commented Dec 3, 2017

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Dec 3, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality workbench-run-as-admin Issues concerning running as administrator
Projects
None yet
Development

No branches or pull requests

5 participants