Description Jed Brown 2010-09-26 16:35:02 EDT

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