/www/tags/NOV_07_2009/htdocs/42docs/users-guide/starting-any-os.html
HTML | 49 lines | 49 code | 0 blank | 0 comment | 0 complexity | f4141d9fba9d1e595b8f0de3a33e5409 MD5 | raw file
Possible License(s): BSD-3-Clause, AGPL-1.0, Apache-2.0, LGPL-2.0, LGPL-3.0, GPL-2.0, CC-BY-SA-3.0, LGPL-2.1, GPL-3.0, MPL-2.0-no-copyleft-exception, IPL-1.0
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Platform-Independent Instructions</title><meta name="generator" content="DocBook XSL Stylesheets V1.65.1"><link rel="home" href="index.html" title="jEdit 4.2 User's Guide"><link rel="up" href="starting.html" title="Chapter 2. Starting jEdit"><link rel="previous" href="starting.html" title="Chapter 2. Starting jEdit"><link rel="next" href="starting-windows.html" title="Starting jEdit on Windows"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Platform-Independent Instructions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="starting.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Starting jEdit</th><td width="20%" align="right"> <a accesskey="n" href="starting-windows.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="starting-any-os"></a>Platform-Independent Instructions</h2></div></div><div></div></div><p>
- Exactly how jEdit is started depends on the operating system. For example, on Unix you can run “<span class="quote">jedit</span>” at the command line,
- or select jEdit from a menu; on Windows, you can
- use the jEditLauncher package, which is documented in
- <a href="starting-windows.html" title="Starting jEdit on Windows">the section called “Starting jEdit on Windows”</a>.
- </p><p>
- If jEdit is started while another copy is already running, control is
- transferred to the running copy, and a second instance is not loaded.
- This saves time and memory if jEdit is started multiple times.
- Communication between instances of jEdit is implemented using
- TCP/IP sockets; the initial instance is known as the
- <i class="firstterm">server</i>, and subsequent invocations are
- <i class="firstterm">clients</i>.
- </p><p>
- If you find yourself launching and exiting jEdit a lot, the startup time can get a bit bothersome.
- If the <b class="userinput"><tt>-background</tt></b> command line switch is specified,
- jEdit will continue running and waiting for client requests even
- after all editor windows are closed. When run in background mode,
- you can open and close jEdit any number of times, only having
- to wait for it to start the first time. The downside of this
- is increased memory usage.
- </p><p>
- When running on MacOS X, the <b class="userinput"><tt>-background</tt></b> command-line switch is active by default, so that jEdit conforms to the platform convention that programs should stay open until the <span><b class="guimenuitem">Quit</b></span> command is explicitly invoked by the user, even if all windows are closed. To disable background mode on MacOS X, use the <b class="userinput"><tt>-nobackground</tt></b> switch.
- </p><p>
- For more information about command line switches that control the
- server feature, see <a href="cli-usage.html" title="Command Line Usage">the section called “Command Line Usage”</a>.
- Note that if you are using <span class="application">jEditLauncher</span>
- to start jEdit on Windows, this switch cannot be specified on the
- MS-DOS prompt command line when starting jEdit; it must be set as described
- in <a href="launcher-starting.html" title="Starting jEdit">the section called “Starting jEdit”</a>.
- </p><p>
- jEdit remembers open buffers, views and split window configurations between editing sessions, so you can get back to work immediately after starting jEdit. This feature can be
- disabled in the <span><b class="guibutton">General</b></span> pane of the
- <span><b class="guimenu">Utilities</b></span>><span><b class="guimenuitem">Global Options</b></span>
- dialog box see <a href="global-opts.html#general-pane" title="The General Pane">the section called “The General Pane”</a>.
- </p><div class="sidebar"><p class="title"><b>The edit server and security</b></p><p>
- Since Java does not provide any interprocess communication facility other than TCP/IP, jEdit takes extra precautions to prevent remote attacks.
- </p><p>
- Not only does the edit server pick a random TCP port number on startup,
- it also requires that clients provide an <i class="firstterm">authorization
- key</i>; a randomly-generated number only accessible to
- processes running on the local machine.
- So not only will “<span class="quote">bad guys</span>” have to guess a 64-bit integer,
- they will need to get it right on the first try; the edit server
- shuts itself off upon receiving an invalid packet.
- </p><p>
- In environments that demand absolute security, the edit server can be
- disabled by specifying the <b class="userinput"><tt>-noserver</tt></b> command line switch.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="starting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="starting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="starting-windows.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Starting jEdit </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Starting jEdit on Windows</td></tr></table></div></body></html>