Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

freemind(1) [debian man page]

FREEMIND(1)						      General Commands Manual						       FREEMIND(1)

NAME
freemind -- A Java program for creating and viewing mindmaps. SYNOPSIS
freemind [no_options] DESCRIPTION
This manual page documents briefly the freemind command. This manual page was written for the Debian distribution because the original program does not have a manual page. Instead, it has docu- mentation as a mindmap (see Help menu in FreeMind). freemind is a program that allows to create and view so-called mindmaps, as well as export them to HTML or different image formats. It also has a plugin concept to extend its functionality. OPTIONS
This program does not have any option. Just start it! ENVIRONMENT VARIABLES
DEBUG If this environment variable is set, freemind gives more information on how it finds its different elements, as well as some other information. JAVACMD Default value for the java virtual machine (the java command). JAVA_BINDIR If $JAVACMD is not set, the java virtual machine is searched under $JAVA_BINDIR/java. JAVA_HOME If $JAVACMD and $JAVA_BINDIR are not set, the java virtual machine is searched under $JAVA_HOME/bin/java. PATH If all $JAVA... environment variables fail, the java virtual machine command (java) is searched in the $PATH (with which). CLASSPATH ADD_JARS The $CLASSPATH variable also lets one specify additional jars, which is good, if you want to add a new Look&Feel jar (the motif one is so ugly...). Alternatively, the content of $ADD_JARS will be prepended to $CLASSPATH. FREEMIND_BASE_DIR Directory where FreeMind searches for its plugins and libraries FILES
/etc/freemind/freemindrc ~/.freemind/freemindrc freemind tries to read its environment variables from /etc/freemind/freemindrc and ~/.freemind/freemindrc, so that specific set- tings are possible at machine and user level. /usr/bin/java If all searches through environment variables fail, the java virtual machine is expected to be /usr/bin/java; if not, freemind exits with an error. SEE ALSO
The online documentation under http://freemind.sf.net/, especially the Linux related one under the Wiki page link http://freemind.source- forge.net/wiki/index.php/FreeMind_on_Linux. AUTHOR
This manual page was written by Eric Lavarde deb@zorglub.s.bawue.de for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version pub- lished by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. FREEMIND(1)

Check Out this Related Man Page

JAVA-WRAPPERS(7)						   Java wrappers						  JAVA-WRAPPERS(7)

NAME
java-wrappers - capacities shared by java wrapper scripts DESCRIPTION
Most Java programs are not run directly, but through small shell scripts that take care of various things, such as finding a suitable java environment and looking for libraries. To ease the task of the maintainers, they rely on a library providing runtime detection, library detection and other features. This manual page describes the common features of all those scripts, and to which point you can configure them. This is mainly done via environment variables. ENVIRONMENT VARIABLES
java-wrappers understands some environment variables: JAVA_CMD The java command that will be run. If this variable is set, it disables all lookup for a java runtime. JAVA_BINDIR Specifies a directory that will be looked for a java or a jdb executable (depending on the setting of JAVA_DEBUGGER). It has prece- dence over JAVA_HOME but not over JAVA_CMD. JAVA_HOME A path to a java runtime. If this variable is set, all lookup for a java runtime is disabled, except that if no java executable is found in the path, the command java is used. JAVA_FLAVOR A probably more easy-to-use version of the JAVA_HOME variable: instead of specifying the full path of the java runtime, you name it. List of available flavors can be found in the file /usr/lib/java-wrappers/jvm-list.sh. See examples below. JAVA_DEBUGGER If this is set, the wrapper will try to pick up a java debugger rather than a java interpreter. This will fail if the jbd of the runtime found is a stub. JAVA_CLASSPATH Additional classpath, will have priority over the one found by the wrapper. JAVA_ARGS Additional arguments to the java command. They will come before all other arguments. FORCE_CLASSPATH If this variable is set, it will be the only classpath. You'd better know what you are doing. DEBUG_WRAPPER This is probably the most important variable; if it set, the wrapper will print out useful information as it goes by its business, such as which runtime it did find, and which command is run eventually. JAVA_JARPATH The path where the wrappers will go looking for jar archives. If not set, the wrapper will look into the default directory, /usr/share/java. Warning : the wrapper will not look anywhere else than in JAVA_JARPATH. Setting it incorrectly will most probably result in early crashes. EXAMPLES
The examples all rely on rasterizer(1), from the package libbatik-java, but they really apply to all scripts that use java-wrappers. Print out debugging information: DEBUG_WRAPPER=1 rasterizer Limit rasterizer's memory to 80 MB: JAVA_ARGS=-Xmx80m rasterizer Force rasterizer to run with kaffe(1): JAVA_HOME=/usr/lib/kaffe rasterizer The same, but using JAVA_BINDIR: JAVA_BINDIR=/usr/lib/kaffe/bin rasterizer Force rasterizer to run with openjdk: JAVA_FLAVOR=openjdk rasterizer Debug rasterizer with Sun's debugger, while printing debugging information from the wrapper: DEBUG_WRAPPER=1 JAVA_CMD=/usr/lib/jvm/java-6-sun/bin/jdb rasterizer BUGS
Care has been taken to make the wrappers bug-free. If that was not the case, please file a bug report against the java-wrappers package. If you wish to submit any problem with a java executable relying on java-wrappers, please also submit the output of the command run with DEBUG_WRAPPER=1. It will save one mail exchange and therefore potentially reduce the time it takes to fix the bug. DEVELOPERS
There is currently no documentation about writing a wrapper script save the comments in /usr/lib/java-wrappers/java-wrappers.sh. If you have to write one, we suggest you base yourself upon, for instance, the rasterizer wrapper script, or any other one (just pick up any direct reverse dependency of java-wrappers and look for scripts). SEE ALSO
java(1), jdb(1) /usr/lib/java-wrappers/java-wrappers.sh AUTHOR
java-wrappers and its documentation were written by Vincent Fourmond <fourmond@debian.org> Version 0.1.16 2010-05-04 JAVA-WRAPPERS(7)
Man Page