Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 506960 - [misc] Text editor should not prompt for replace reload if auto-refresh is enabled, even for external non-workspace files
Summary: [misc] Text editor should not prompt for replace reload if auto-refresh is en...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-03 05:43 EDT by Michael Vorburger CLA
Modified: 2020-02-01 10:30 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Vorburger CLA 2016-11-03 05:43:50 EDT
Bug 248068 fixed "Text editor should not prompt if auto-refresh is enabled" 5.5 years ago in 3.7 already. This works great, except in one case:

For text files opened directly from the file system, not in a project in the workspace, Eclipse even in Version: Neon.1a Release (4.6.1) Build id: 20161007-1200 still prompts the user with the annoying old friend "File Changed: The file '...0 has been changed on the file system. Do you want to replace the editor contents with these changes?" - even with [X] Refresh using native hooks or polling and [X] Refresh on access enabled.

This isn't as consistent as it could be (why different behaviour for files in-workspace and external files?), and ... annoying (as it was for files in the workspace, which was fixed with Bug 248068).


A workaround is to just create a .project where I'd like to open something like e.g. a simple todo.txt (which also frequently externally modified, e.g. by http://todotxt.com ..) and open that project - but having to go through this hoop just to get auto-refresh seems dumb.
Comment 1 Eclipse Genie CLA 2020-02-01 10:30:55 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.