Community
Participate
Working Groups
Usually zip, bat & exe files are not associated with internal eclipse editors. So when I use the Open Resource dialog and search for such a resource & select Open, it actually opens Winzip, or runs the batch file & so on. That by itself is scary, but what I am asking for is that the resource that is opened be revealed in Navigator, Package Explorer or Project Explorer IF the link with editor option is turned on in those views. Currently only if the file opens in an internal eclipse editor and the link with editor is ON, the resource is revealed. Perhaps there should be an option in the dialog to just reveal the resource (especially if I want to know the path of the resource but not necessarily open it), currently you have to look at the status and copy the value.
Hmmm, the current semantics of 'Open Resource' are fairly clear...open the editor onto the selected resource. This sounds more like you want a 'Find Resource' command associated with the various Explorers, I'd be leery of complicating the current code (of course there is likely a fair bit of overlap in the actual code but that's orthogonal to whether or not there are two separate commands...
Hmm... Enable "Link with Editors" in the package explorer/project explorer. Open "Open Resource..." dialog, select any *.txt file and open it. An internal editor will be opened and the resource will be highlighted in the package explorer/project explorer. Do the same for *.zip file. The file will be opened by an external application, but the resource will not be highlighted in the explorer. What is, as I understand, Raj's issue. This is an UI issue. I'm reassigning it back to UI.
I would like to have an "Open With..." option on the Open Resource dialog. We probably have a bug for this already.
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.
