From: Ed Stewart <estewart@vn...> - 2001-08-29 22:27:49
Thanks for the input. The problem actually went away after a hard reboot, so
after reading your reply I believe the problem may have been a stale server
file. Works like a charm now (although with the new "Open with jEdit"
Explorer extension, I don't even need the SendTo shortcut now). Now all
methods use the already existing instance.
A couple of suggestions:
(1) Your jEdit settings directory contains a file named "server" while the
application is running. The launcher uses this file to connect with a
server socket jdit makes available. If you use default parameters for
jEdit, the settings directory will be found in something like
run jEdit.getSettingsDirectory() in BeanShell if you are having trouble
finding it. If jEdit is not running and you find a "server" file, delete it
before restarting jEdit. This has solved similar problems in the past.
(2) When closing jEdit, use the application's quit action or close the jEdit
frame window. If you use java.exe to run jEdit and close its console
window, or if you force termination with the Task Manager, the launcher may
have problems the next time it runs, because deletion of hte "server" file
is part of an orderly shutdown.
I haven't hear of anyone using the "SendTo" feature with jEdit, but I just
successfully tested an application shortcut to [jEdit directory]\jedit.exe
placed in the user's \Send To directory.
Let me know if you still have problems.
jEdit Users' List