You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
potasiyam opened this issue
Jan 7, 2016
· 6 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
I have noticed that if a file is open in code and the file is changed externally, there is no way to know about it until I try to save it. I feel that if the file on the disk and file opened on code is in same state it should automatically reflect the changes made on the disk. This is what every modern text editor do.
Here is how to reproduce it.
Create a text file.
Open the file in Sublime text, Bracket and Code. In this situation the file is blank in all 3 editors.
In Sublime text, write "Hello". Then save.
Switch to Bracket, You will see "Hello".
Switch to Code, you will see blank.
Now again switch to Bracket, write "Hello world". Then save.
Switch to Sublime text, You will see "Hello world".
Switch to Code, you will see blank.
In both cases Code should reflect the changes made on disk.
The text was updated successfully, but these errors were encountered:
I think in your case you opened just a file, can you try the same thing with opening its parent folder and see if then the updates happen? Also, is this G: drive something you created with SUBST or a real physical drive?
Opening the parent folder solves it. I created a folder then put the file in there and opened the folder in code. Now it updates immediately with external changes.
My G: drive is a physical drive.
So it doesn't work with single files, right?
I can reproduce, this only seems to happen for files that are on the root of the disk: nodejs/node#4643
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
Jan 12, 2016
bpasero
changed the title
Opened file in Code is not updated immidietely when changed externally
Cannot watch for file changes for files on disk root
Jan 12, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
Code version: 0.10.6
OS: Windows 10 x64
I have noticed that if a file is open in code and the file is changed externally, there is no way to know about it until I try to save it. I feel that if the file on the disk and file opened on code is in same state it should automatically reflect the changes made on the disk. This is what every modern text editor do.
Here is how to reproduce it.
In both cases Code should reflect the changes made on disk.
The text was updated successfully, but these errors were encountered: