PageRenderTime 53ms CodeModel.GetById 30ms app.highlight 6ms RepoModel.GetById 14ms app.codeStats 1ms


HTML | 49 lines | 49 code | 0 blank | 0 comment | 0 complexity | f4141d9fba9d1e595b8f0de3a33e5409 MD5 | raw file
 1<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>
 2   Exactly how jEdit is started depends on the operating system. For example, on Unix you can run &#8220;<span class="quote">jedit</span>&#8221; at the command line,
 3   or select jEdit from a menu; on Windows, you can
 4   use the jEditLauncher package, which is documented in
 5   <a href="starting-windows.html" title="Starting jEdit on Windows">the section called &#8220;Starting jEdit on Windows&#8221;</a>.
 6  </p><p>
 7   If jEdit is started while another copy is already running, control is
 8   transferred to the running copy, and a second instance is not loaded.
 9   This saves time and memory if jEdit is started multiple times.
10   Communication between instances of jEdit is implemented using
11   TCP/IP sockets; the initial instance is known as the
12   <i class="firstterm">server</i>, and subsequent invocations are
13   <i class="firstterm">clients</i>.
14  </p><p>
15   If you find yourself launching and exiting jEdit a lot, the startup time can get a bit bothersome.
16   If the <b class="userinput"><tt>-background</tt></b> command line switch is specified,
17   jEdit will continue running and waiting for client requests even
18   after all editor windows are closed. When run in background mode,
19   you can open and close jEdit any number of times, only having
20   to wait for it to start the first time. The downside of this
21   is increased memory usage.
22  </p><p>
23   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.
24  </p><p>
25   For more information about command line switches that control the
26   server feature, see <a href="cli-usage.html" title="Command Line Usage">the section called &#8220;Command Line Usage&#8221;</a>.
27   Note that if you are using <span class="application">jEditLauncher</span>
28   to start jEdit on Windows, this switch cannot be specified on the
29   MS-DOS prompt command line when starting jEdit; it must be set as described
30   in <a href="launcher-starting.html" title="Starting jEdit">the section called &#8220;Starting jEdit&#8221;</a>.
31  </p><p>
32   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
33   disabled in the <span><b class="guibutton">General</b></span> pane of the
34   <span><b class="guimenu">Utilities</b></span>&gt;<span><b class="guimenuitem">Global Options</b></span>
35   dialog box see <a href="global-opts.html#general-pane" title="The General Pane">the section called &#8220;The General Pane&#8221;</a>.
36  </p><div class="sidebar"><p class="title"><b>The edit server and security</b></p><p>
37    Since Java does not provide any interprocess communication facility other than TCP/IP, jEdit takes extra precautions to prevent remote attacks.
38   </p><p>
39    Not only does the edit server pick a random TCP port number on startup,
40    it also requires that clients provide an <i class="firstterm">authorization
41    key</i>; a randomly-generated number only accessible to
42    processes running on the local machine.
43    So not only will &#8220;<span class="quote">bad guys</span>&#8221; have to guess a 64-bit integer,
44    they will need to get it right on the first try; the edit server
45    shuts itself off upon receiving an invalid packet.
46   </p><p>
47    In environments that demand absolute security, the edit server can be
48    disabled by specifying the <b class="userinput"><tt>-noserver</tt></b> command line switch.
49   </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>