|
From: John G. <jge...@ny...> - 2001-06-27 14:22:50
|
>
> I recently updated jEdet from 3.1 final to 3.2 pre3. And now
> jEdit starts in
> a new instance even if i have a copy in memory. I tested the file
> "~home/.jedit/server" on my computer. It overrides each time when jEdit
> starts.
>
> PS. I use NT4 sp6 & SUN JDK 1.3.1.
>
There are two problems here. The first is that the second copy of jEdit
tries to connect to the first copy's EditServer using the wrong IP address.
The address of the EditServer was recently changed to
InetAddress.getByName("127.0.0.1"), but in the startup code, contact is
attempted on the former version's address, InetAddress.getLocalHost(). This
will return an external IP address if one exists, so the connection attempt
fails. To fix this, jEdit.java:170 (version 3.2pre3) should be changed to
provide the correct InetAddress call.
The second problem made it tougher to find the cause of the first. When the
second copy tries to connect to the EditServer, its Activity Log has not yet
been initialized, so the lengthy, hardcoded message in jEdit.main()
regarding a connection failure is never written to the log. The Activity Log
initialization code could be moved to an earlier point in jEdit.main().
Alternatively, an EditServer connection failure could set a flag that the
startup routine could examine after the Activity Log is initialized.
John
|