#6 problem with windows install?

open
nobody
None
5
2003-06-04
2002-11-01
Anonymous
No

Using windows 2000:

Two issues here (probably related?)

Jedit starts OK, but "jelaunch.log" in the JEDIT program
directory gives errors:

Debug : [launcher] searching for server file
C:\Documents and Settings\mclark\.jedit\server
Debug : [launcher] Server file not opened
Debug : [launcher] System error message: The
system cannot find the file specified.

My JEDIT shell32 context menus are also broken
(spawns JEDIT but does not open the file requested)

Possible cause? ! :

have moved my desktop location to "d:\storage\desktop"
instead of the default "c:\documents and
settings\username\desktop"

Jedit has placed all my downloaded plugins into
d:\storage\desktop\.jedit\jars (leading my to believe that
jedit finds its home there), yet LAUNCHER is looking
for "server" file in "c:\documents and
settings\mclark\.jedit" which is not living there.

What to do? Perhaps it's just a configuration issue.
Seems like it should automatically detect this
environment though.

~~ mclark at godze.us ~~

Discussion

  • John Gellene
    John Gellene
    2002-11-03

    Logged In: YES
    user_id=117073

    How does the OS know the desktop location? A workaround
    for your problem would be to set the -settings command line
    variable to the location of the settings folder:

    -settings=D:\storage\desktop\.jedit

     
  • Slava Pestov
    Slava Pestov
    2003-06-04

    • labels: 103010 -->
    • milestone: 101608 -->
     
  • Martin Jericho
    Martin Jericho
    2003-11-14

    Logged In: YES
    user_id=419287

    Java determines the user.home property by taking the parent
    directory of the desktop. (see src\j2se\src\win32
    \native\java\lang\java_props_md.c)
    As far as I'm aware this is not documented anywhere.

    jEditLauncher should use the same technique to determine
    the home directory, so this is a bug.

     
  • Martin Jericho
    Martin Jericho
    2003-11-14

    Logged In: YES
    user_id=419287

    The only workaround that works for me is to add the following
    parameter to the Command line options for Java Application
    Loader:
    -Duser.home="C:\Documents and Settings\mjericho"