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.

Sign up for GitHub

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

Jump to bottom

Updating a sym-link file outside is not getting updated in Multi-root workspace #29631

Closed
sandy081 opened this issue Jun 27, 2017 · 3 comments
Closed

Updating a sym-link file outside is not getting updated in Multi-root workspace #29631

sandy081 opened this issue Jun 27, 2017 · 3 comments
Assignees
@Tyriar
Labels
bug Issue identified by VS Code Team member as probable bug file-watcher File watcher macos Issues with VS Code on MAC/OS X *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Backlog

Comments

@sandy081
Copy link
Member

Testing #29478

  • Set up multi workspace with two Folders A and B. Assume that B has .vscode/settings.json file.
  • Create a sym link in B/.vscode folder named symlink-settings.json pointing to settings.json
  • Open Folder B in VS Code separately, from now I call single root workspace.
  • Open symlink-settings.json in both workspaces
  • Update the file in single root workspace

Expected that sym link file is also updated in multi root workspace. But not.
@vscodebot vscodebot bot added the workbench label Jun 27, 2017
@sandy081 sandy081 assigned Tyriar and unassigned bpasero Jun 27, 2017
@sandy081 sandy081 added the workbench-multiroot Multi-root (multiple folders) issues label Jun 27, 2017
@bpasero bpasero added the file-watcher File watcher label Jun 27, 2017
@Tyriar Tyriar added the macos Issues with VS Code on MAC/OS X label Jun 27, 2017
@Tyriar Tyriar added this to the July 2017 milestone Jun 27, 2017
@Tyriar Tyriar mentioned this issue Jul 21, 2017
Open
@Tyriar
Copy link
Member

Tyriar commented Jul 21, 2017

Created Axosoft/nsfw#30

@Tyriar Tyriar added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jul 21, 2017
@Tyriar Tyriar modified the milestones: Backlog, July 2017 Jul 21, 2017
@bpasero bpasero removed workbench workbench-multiroot Multi-root (multiple folders) issues labels Nov 16, 2017
@Tyriar Tyriar added the bug Issue identified by VS Code Team member as probable bug label Dec 23, 2017
@Tyriar
Copy link
Member

Tyriar commented Sep 12, 2018

Closing this as it's minor and tracked upstream.

@Tyriar Tyriar added the *out-of-scope Posted issue is not in scope of VS Code label Sep 12, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 12, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Tyriar Tyriar

Labels
bug Issue identified by VS Code Team member as probable bug file-watcher File watcher macos Issues with VS Code on MAC/OS X *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@bpasero @Tyriar @sandy081