Community
Participate
Working Groups
Not sure of component, please reassign as necessary... Select Window -> Preferences -> Workbench -> File Associations. Click Add button for Associated Editors. Among others the list of the editors contains two following entries: "No Source Found" "Source Not Found Editor" (see screencapture). Associate it with a .java file and then open a .java file. All you see is in red text, the path to the java file. Is there anything more to these editors than this?
Created attachment 19564 [details] screenshot
These editors are displayed when debugging and no source is found. It allows the user to edit your source lookup path. I agree they don't make sense in the pref pages, but that may be a workbench issue - i.e. I don't know of a way to make an editor "private" so it does not appear in the file association list. Moving to UI for comment.
There isn't a way to do this and it doesnt strike me that it's worth adding API to accomplish this. Doug?
It might be worth adding API for this, but it is low priority.
Is it okay to leave the "TVT..." in the title? We are using this for tracking purposes. Thanks. And the severity level change is fine with us.
I need to understand your process better than. If it is marked TVT will it still be brought up as an open nl issue for 3.1.1? If so then you should remove the tag. I am not bothered so long as the nl team does not get confused by this. BTW there is an nl tag that might solved this issue - if the nl team search on that tag it might be easier.
Moving Dougs bugs
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] component area.
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. If you have further information on the current state of the bug, please add it. 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.
