Bugzilla – Full Text Bug Listing
| Summary: | Open File from command line starts new instance after new session is accidentally started | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jed Brown <jed> |
| Component: | IDE | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer, ob1.eclipse, pwebster, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
This is probably a duplicate of bug 316821 (In reply to comment #1) > This is probably a duplicate of bug 316821 +1, it does seem to be the same issue. *** This bug has been marked as a duplicate of bug 316821 *** |
Build Identifier: Build id: I20100921-1024 The primary problem is that it is possible for a running session to get "lost" so that files can no longer be opened from the command line. Unknown command line options are also not warned about (I would prefer this over the very heavy and probably not desirable opening of a new session). It would also be standard behavior for "eclipse path/to/newfile" to create a new file at that path rather than an error. Reproducible: Always Steps to Reproduce: $ ls -l `which indigo` lrwxrwxrwx 1 jed users 41 Sep 26 21:46 /home/jed/bin/indigo -> /home/jed/src/eclipse-3.7/eclipse/eclipse $ indigo & # Wait for it to start up $ touch a.txt $ indigo a.txt # opens in running session (good) $ indigo b.txt # file does not exist, eclipse dialog tells me so $ indigo -unknown # starts a new session (normal speed), does not warn about unknown option # dialog says "Workspace in use or cannot be created, choose a different one # I click "OK" (no choice), get a dialog to choose a # workspace, I press cancel $ indigo a.txt # This file exists, I still have my original running instance. # Nonetheless, a new instance starts, but very slowly # (about 1 minute to give startup screen), complains about # the workspace being in use