Bug 506496 - Support `eclipse /path/to/file` without --launcher.openFile
Summary: Support `eclipse /path/to/file` without --launcher.openFile
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: feep
Depends on:
Blocks:
 
Reported: 2016-10-25 07:20 EDT by Mickael Istria CLA
Modified: 2016-12-06 13:27 EST (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2016-10-25 07:20:58 EDT
As they're not aware of the need for the ` --launcher.openFile` option, regular users try either `eclipse /path/to/file` and are disappointed to see it not working. Similarly, if they try their OS "Open With" feature, the OS doesn't know about the flag neither, so ends up trying `eclipse /path/to/file` as well.
In order to make this feature much more usable and used, we need to get rid of the need to have that flag.
Comment 1 Mickael Istria CLA 2016-10-25 07:23:00 EDT
Tentative for 4.7.
Comment 2 Mikaël Barbero CLA 2016-11-24 05:20:57 EST
The "open with" feature works at least on macOS. What about Linux and Windows? 

IMO the "open with" feature is much more desirable than the ability to edit a file with "eclipse /path/to/file". However, I understand that it may be necessary to have it to have the OS level feature.
Comment 3 Mickael Istria CLA 2016-11-24 05:26:33 EST
(In reply to Mikaël Barbero from comment #2)
> The "open with" feature works at least on macOS. What about Linux and
> Windows? 

From which installation? Installer, packages, dmg...?

> IMO the "open with" feature is much more desirable than the ability to edit
> a file with "eclipse /path/to/file".

Well, I've got different people reporting that `eclipse /path/to/file` from a command-line is very desired. Here is an example: https://twitter.com/dougschaefer/status/799284690729439233 (not that it would also require to fix bug 500388)
Comment 4 Mikaël Barbero CLA 2016-11-24 06:38:43 EST
(In reply to Mickael Istria from comment #3)
> (In reply to Mikaël Barbero from comment #2)
> > The "open with" feature works at least on macOS. What about Linux and
> > Windows? 
> 
> From which installation? Installer, packages, dmg...?

An installation provisioned by Oomph.

> 
> > IMO the "open with" feature is much more desirable than the ability to edit
> > a file with "eclipse /path/to/file".
> 
> Well, I've got different people reporting that `eclipse /path/to/file` from
> a command-line is very desired. Here is an example:
> https://twitter.com/dougschaefer/status/799284690729439233 (not that it
> would also require to fix bug 500388)

I'm sure people used to CLI are willing to have this, and I don't deny its usefulness (I would like it too). I just would like to say that the "open with" OS feature probably targets a larger audience than the "eclipse /path/to/file". And I may be wrong ;)
Comment 5 Martin Oberhuber CLA 2016-11-24 09:09:44 EST
Hmm, isn't this supposed to be already covered with the
   --launcher.defaultAction openFile
in the eclipse.ini file ?

I remember the times when this was implemented, so I honestly thought it was already resolved. If it is not, then it might make sense being more specific about what is missing or not working (eg point to dependent bugs).

For "Open With" on Windows, IIRC some Registry Keys need to be set by some sort of installer (or on the first launch of Eclipse).
Comment 6 Mickael Istria CLA 2016-11-24 09:17:12 EST
(In reply to Martin Oberhuber from comment #5)
> Hmm, isn't this supposed to be already covered with the
>    --launcher.defaultAction openFile
> in the eclipse.ini file ?

Ok, last time I tried, this was not working. Or maybe I tried on a directory and this drove me to wrong conclusions. I cannot remember.
Now I tried again `./eclipse eclipse.ini` and I get an error because workspace is already in use.
Comment 7 Mickael Istria CLA 2016-11-30 12:37:50 EST
The current state already allows what's required. The minor issue I have need to be verified (as I'm using Fedora 25 which has a major change in windowing, those might be caused by Fedora) and if I find some actual issues, they should be reported separately and wouldn't make much sense in FEEP.