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
Describe the bug
Editing files in USS I double click to edit and close, e.g. /u/myuserid/myfile.txt
I then use the filter to select a different directory from favourites and open /u/myuserid/temp/myfile.txt.
The file that opens is the previous one with the same name.
The same occurs when I edit and save and close a file editor, and then behind the Zowe Explorer I update that file (perhaps through VI or ISPF 3.17
To Reproduce
Edit a file, close it, edit another file with the same name.
Expected behavior
Once a file editor is closed clear the cache.
I know there is a button "Pull from mainframe" however this isn't obvious to customers to use.
The expected behavior should be that once an editor is closed the local copy is lost, and also that if I open two files with the same name in different paths I get each unique file, rather than the same contents
The text was updated successfully, but these errors were encountered:
Describe the bug
Editing files in USS I double click to edit and close, e.g.
/u/myuserid/myfile.txt
I then use the filter to select a different directory from favourites and open
/u/myuserid/temp/myfile.txt
.The file that opens is the previous one with the same name.
The same occurs when I edit and save and close a file editor, and then behind the Zowe Explorer I update that file (perhaps through VI or ISPF 3.17
To Reproduce
Edit a file, close it, edit another file with the same name.
Expected behavior
Once a file editor is closed clear the cache.
I know there is a button "Pull from mainframe" however this isn't obvious to customers to use.
The expected behavior should be that once an editor is closed the local copy is lost, and also that if I open two files with the same name in different paths I get each unique file, rather than the same contents
The text was updated successfully, but these errors were encountered: