Community
Participate
Working Groups
Launch Eclipse editor from outside Eclipse. Applications would like to provide file extension associations so that double-clicking on a file in the OS desktop would open the associated Eclipse editor. (This plan item was split off from 3.0 plan item bug 37935)
Isn't this a dup of bug 47487 (which already has some votes on it)?
It's not quite a duplicate. This is a special "plan item" bug report to help us track plan items. I'll annotate 47487 to mention this one.
Text cannot support this unless there is support to associate an editor with the clicked file.
There will have to be some runtime/startup support for this too. If you can get some of the hooks/support/design/framework in, even if it's not fully supported in 3.0 then that would be helpful. For example, a built-in ability to programatically make a running Eclipse go to a certain file path and line number from the outside would go a long way. One suggestion on how to do this - have eclipse.exe take special arguments that would make it communicate to a running process so I could say something like "eclipse.exe -file c:\temp\file.java -line 15" or "eclipse.exe - command 'open c:\temp\file.java:15' (I just made that syntax up so don't take that as a requirement). Building it into the startup program would be better than, say, publishing a socket that you could write commands to (the way I did in the fileopen project on eclipsepowered.org) because then the socket and the commands would become API that could never change. The startup program would be free to use different communication mechanisms if it wanted, for example DDE or shared memory on Windows, pipes or sockets on Unix, etc., and it would have a better chance of handling the case where there are multiple eclipse instances running.
Deferring.
I believe the original and still open bug for this is Bug 4922, which has been hanging around since 2001. This "plan item" has been languishing for over a year. Is it really in any plan? For what release? A couple of points I haven't seen made: - How running programs get notice to open files is platform-dependent. I doubt that any part of it will or should ever be API. That doesn't preclude someone contributing a solution that works for a given platform without trying to solve the problem for every platform. - Any solution should also work with RCP applications and products. Among other things, this means it shouldn't be hard-wired to a particular resource, location or port.
*** Bug 112777 has been marked as a duplicate of this bug. ***
I think this should be marked as a duplicate of bug 4922 or vice-versa. There are several open bugs for this feature, which causes the CC list and votes to become fragmented.
This is no longer a plan item.
I think a much better place for consolidating the votes and CC lists would be bug #178927 filed against Equinox, for adding a generic extensible solution for "remote commands to be executed in an already running application", to be added right to the Equinox / Launcher framework. The Launcher is more generally applicable, extensible, and has an easier job launching the application to receive a remote command in case it is not already running. Could the 9 voters consider also voting on bug #178927 in order to foster this approach?
I believe this is normal for any serious programmers IDE to have files opened in it by associations. Honestly, eclipse is the FIRST IDE that DOES NOT DO that, so the reason why it is missing is under a veil of secrecy, as I feel it. That is not my choice to use eclipse (moreover, I don't like it because of many-many reasons), it is rather my "project restriction" and I am missing this feature a lot. Please help me to make my work efficiently!
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] component area.
This is asking for the same thing as bug 4922. http://wiki.eclipse.org/Eclipse/OpenFileFeature *** This bug has been marked as a duplicate of bug 4922 ***
