Re: [ jEdit-users ] JEdit menu icon on Linux ...

[mike d. <md...@je...>]

begin Joshua Miller quotation:
> I've just setup a new RedHat 7.3 workstation and while I'm VERY new to
> Linux, I've installed JDK 1.4 as well as JEdit and can get JEdit to
> run, but I'm running into issues getting it to start nicely without
> having to visit the command-line and leave the console open while
> running JEdit.
>  
> When I set the JAVA_HOME variable, it never sticks around.
<snip>
> Can I create a menu item in KDE that either sets the JAVA_HOME and
> then runs jedit or can I create a menu item for jedit at all? I'm
> running KDE 3.0 on RedHat 7.3

I don't think it has been necessary to set JAVA_HOME since jEdit 4.0 (it
was used in earlier versions of the launch script). The current install
code simply outputs the value of the java.home system property at
install time ('out.write(System.getProperty("java.home"))').

You should just be able to create a menu item that runs "jedit". If you
have reason to suspect JAVA_HOME is causing problems besides the outdated
references to JAVA_HOME in the docs, you can set the variable for the
command invocation by making your menu item run "JAVA_HOME=/path/to/java
jedit".

Could you describe in detail to problem you're having launching jEdit
from a menu item? If KDE has a "run command in console" option or
similar, it may help to enable it during testing. I would suspect the
problem is related to the JDK's bin directory not being in the PATH.
This should be set in /etc/profile; mine has the following (make sure
it's before the "export PATH" statement):

	if ! echo $PATH | /bin/grep -q "/usr/java/j2sdk1.4.0/bin" ; then
		PATH="$PATH:/usr/java/j2sdk1.4.0/bin"
	fi

-md