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

Out of workspace files: Changes from git operations not reflected #2592

Closed
constantincerdan opened this issue Jan 31, 2016 · 8 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@constantincerdan
Copy link

As above. I've been testing it out by switching branches in git using terminal and the file does not update. Sublime & Atom do it immediately, but with Code you have to switch out and back into the file in order for it to update.

@bpasero
Copy link
Member

bpasero commented Feb 1, 2016

@constantincerdan on which OS is this? does it work when you edit one of the working files with another editor outside of Code?

I assume the working files are not part of the folder you opened? Or are you not opening a folder at all?

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster labels Feb 1, 2016
@bpasero bpasero added this to the Feb 2016 milestone Feb 1, 2016
@constantincerdan
Copy link
Author

It's on Mac OSX. It doesn't work at all, even when the files are edited using another editor. I haven't opened any folders and have instead opened the file independently.

-----Original Message-----
From: "Benjamin Pasero" notifications@github.com
Sent: ‎01/‎02/‎2016 10:22
To: "Microsoft/vscode" vscode@noreply.github.com
Cc: "Constantin" constantincerdan@gmail.com
Subject: Re: [vscode] Working Files Not Watched (#2592)

@constantincerdan on which OS is this? does it work when you edit one of the working files with another editor outside of Code?
I assume the working files are not part of the folder you opened? Or are you not opening a folder at all?

Reply to this email directly or view it on GitHub.

@bpasero
Copy link
Member

bpasero commented Feb 1, 2016

Weird, works for me. See my recording and maybe see what I need to do different to reproduce:

untitled

@constantincerdan
Copy link
Author

I just tested it now by changing it in a different editor, and this time it did auto update. However, it still doesn't work when switching branches in git (using Terminal). See my recording below:

http://g.recordit.co/HYlpJq5ZSB.gif

@bpasero
Copy link
Member

bpasero commented Feb 2, 2016

I can reproduce and it looks like a bug in node.js: nodejs/node#5039

@bpasero bpasero added upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed info-needed Issue requires more information from poster labels Feb 2, 2016
@bpasero bpasero modified the milestones: Backlog, Feb 2016 Feb 2, 2016
@bpasero bpasero changed the title Working Files Not Watched Working files: Changes from git operations not reflected Feb 2, 2016
@bpasero bpasero changed the title Working files: Changes from git operations not reflected Out of workspace files: Changes from git operations not reflected Jul 5, 2016
@jack-guy
Copy link

jack-guy commented Jul 6, 2016

Apparently this is intended behavior. Maybe chokadir can figure out a fix? I kind of doubt it though...

@bpasero
Copy link
Member

bpasero commented Nov 12, 2016

#15111

@bpasero bpasero closed this as completed Nov 12, 2016
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 12, 2016
@fatonsopa
Copy link

Hi guys,

this is still happening:

npm -v 3.10.10
node -v v6.11.5
MacOS Sierra 10.12.6

The file.watch is triggering the change only once per file. In windows is working perfectly.

Researched a lot but couldn't find a working solution. Any idea?

Thanks,
Faton

@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
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

4 participants