Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316266 - [IDE] When opening a file it should be refreshed if "Refresh automatically" is on
Summary: [IDE] When opening a file it should be refreshed if "Refresh automatically" i...
Status: CLOSED DUPLICATE of bug 248068
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Paul Webster CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-09 06:58 EDT by Hans-Peter Störr CLA
Modified: 2010-11-01 07:09 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Störr CLA 2010-06-09 06:58:52 EDT
Build Identifier: M20090917-0800

Even if you turn on the preference "General/Workspace/Refresh automatically", eclipse displays "Resource out of sync with the file system ... Press 'F5' ..". Of course the whole point of this option is that you never ever want see this message. So eclipse should do a refresh by itself.

This is in practice quite annoying to me and my coworkers and appears regularily in the following cases (and probably more):
- if you open a project and immediately try to open a file (the automatic refresh is not done yet)
- if you open a logfile of a server that is currently running

It would be nice if you could fix this. Thanks so much!

Reproducible: Always

Steps to Reproduce:
1. Turn preference "General/Workspace/Refresh automatically"
2. open a file in the workspace that changes very frequently

To create a file that changes very frequently you can for instance execute
while true; do echo > frequentlychangingfile; done
in a bash.
Comment 1 Hans-Peter Störr CLA 2010-06-09 07:03:08 EDT
Perhaps bug 268797 is somewhat related.
Comment 2 Dani Megert CLA 2010-11-01 07:09:03 EDT

*** This bug has been marked as a duplicate of bug 248068 ***