PageRenderTime 246ms CodeModel.GetById 235ms app.highlight 6ms RepoModel.GetById 1ms app.codeStats 0ms


XML | 411 lines | 406 code | 0 blank | 5 comment | 0 complexity | 71c1b66b77a58552620a3abd70d47d17 MD5 | raw file
  1<?xml version="1.0" encoding="UTF-8"?>
  2<section id="problems">
  3    <title>Problems</title>
  4    <!-- jEdit buffer-local properties:                      -->
  5    <!-- :indentSize=4:noTabs=false:maxLineLen=80:tabSize=4: -->
  6    <!-- :xml.root=faq.xml:                                  -->
  7    <!-- jEdit FAQ                                           -->
  8    <para>This section deals with problems you may experience while using or
  9    installing jEdit. Problems that aren't OS specific are listed under <link
 10    linkend="general-problems"><quote>General Problems</quote></link>.</para>
 11    <qandaset defaultlabel="qanda">
 12        <qandadiv id="general-problems">
 13            <title>General Problems</title>
 14            <qandaentry>
 15                <question id="wont-start">
 16                    <para>jEdit won't start. What should I do?</para>
 17                </question>
 18                <answer>
 19                    <para>If you don't have a clue as to why you cannot run
 20                    jEdit, it's best to perform a step-by-step diagnosis. If it
 21                    never worked before, begin by finding the Java application
 22                    loader you are using: <filename>java.exe</filename>,
 23                    <filename>javaw.exe</filename> or <filename>java</filename>.
 24                    Make sure it is running by entering its full path with the
 25                    <userinput>-h</userinput> parameter in a terminal or console
 26                    window. If you can't find the Java application loader, your
 27                    Java runtime environment package may be missing or
 28                    incomplete.</para>
 29                    <para>Next, find where you have installed jEdit. You should
 30                    look for the file <filename>jedit.jar</filename> which
 31                    contains all of the application's Java class files in a
 32                    compressed archive.</para>
 33                    <para>Once you have both files, run the Java loader with the
 34                    <userinput>-jar</userinput> option and with
 35                    <filename>jedit.jar</filename> as the target. Make sure that
 36                    you either specify full paths for both files or that the
 37                    directories for the files are part of your
 38                    <filename>PATH</filename> environment variable. If jEdit
 39                    does not load at this point, the likely problem is a corrupt
 40                    <filename>jedit.jar</filename> file. Try downloading the
 41                    application again.</para>
 42                    <para>If jEdit does load using this procedure, you need to
 43                    examine the <quote>shortcut</quote> loading mechanism you
 44                    wish to use.</para>
 45                    <para>On Linux and MacOS X, you need to find and examine the
 46                    <filename>jedit</filename> shell script provided by the
 47                    installation routine to confirm that the script's commands
 48                    target the correct files and locations, and that variables
 49                    like <filename>JAVA_HOME</filename> are either defined in
 50                    the script or elsewhere in your shell's environment. Don't
 51                    forget to make sure that the script's file permissions allow
 52                    you to execute it as a shell script.</para>
 53                    <para>On Windows, if you are using a batch script to run
 54                    jEdit, the same points (other than file permissions) apply
 55                    to examining <filename>jedit.bat</filename>. If you are
 56                    using jEditLauncher, run <userinput>jedit /p</userinput> in
 57                    jEdit's installation directory from a command line to get
 58                    the custom loader's setup dialog. Here you can check the
 59                    paths for both the Java application loader and jEdit as well
 60                    as any command line parameters for both programs. Make sure
 61                    that you have placed Java and jEdit options in the correct
 62                    input fields. If the parameters seems correct but jEdit will
 63                    not load with the Windows launcher, try uninstalling and
 64                    reinstalling the launcher by running <userinput>jedit
 65                    /u</userinput> followed by <userinput>jedit
 66                    /i</userinput>.</para>
 67                    <bridgehead>But it worked before! It just stopped working
 68                    after an upgrade. What should I do?</bridgehead>
 69                    <para>If it used to work for an older version and no longer
 70                    works, it could be that you have some old crud in your jEdit
 71                    settings directory (<literal>$HOME/.jedit</literal>). You
 72                    may want to try renaming the offending file/subdirectory to
 73                    something else, and restarting jEdit with fresh settings.
 74                    You can later copy the old settings back into the previous
 75                    location if you find you are missing things. Many files in
 76                    your settings directory directory are (or should be)
 77                    human-readable/editable, so you are encouraged to examine
 78                    them and see what is there. You can wipe out
 79                    <literal>.jedit/jars-cache</literal> while jEdit is not
 80                    actually running, and it will be rebuilt next time you start
 81                    it.</para>
 82                    <para>If at this point you're still stuck, ask for help on
 83                    the jedit-users mailing list, the jEdit Community
 84                    <quote>Installation</quote> message board or on IRC. You're
 85                    bound to find someone quickly.</para>
 86                </answer>
 87            </qandaentry>
 88            <qandaentry>
 89                <question id="start-missing-plugins">
 90                    <para>After jEdit starts, I can't see all of the plugins I
 91                    have downloaded. How can I make them appear?</para>
 92                </question>
 93                <answer>
 94                    <para>If you use jEdit's Plugin Manager to download and
 95                    install plugins, your plugins will be found in the
 96                    <filename>jars</filename> subdirectory of one of two
 97                    directories: either the directory in which jEdit is
 98                    installed, or the current user's settings directory. These
 99                    are the only location jEdit examines when it loads plugins
100                    at startup.</para>
101                    <para>The default location of the settings directory depends
102                    on your operating system. You can find out its location
103                    during a jEdit session by evaluating
104                    <userinput>jedit.getSettingsDirectory()</userinput> in
105                    BeanShell.</para>
106                    <para>The settings directory can be changed by using the
107                    <userinput>-settings</userinput> command line parameter. If
108                    you change the location of the settings directory with this
109                    parameter, jEdit will not be able to find plugin archive
110                    files in the old location. If you use or change the
111                    <userinput>-settings</userinput> parameter, make sure your
112                    plugins don't get left behind.</para>
113                </answer>
114            </qandaentry>
115            <qandaentry>
116                <question id="problems-out-of-memory">
117                    <para>During an editing session I get an error message about
118                    an <quote>OutOfMemoryError</quote> while working with a
119                    large file or performing a lengthy operation. The message
120                    reappears every time I retry the operation. How can I
121                    prevent this?</para>
122                </question>
123                <answer>
124                    <para>One solution that often works is to set or increase
125                    the allocation of memory to the heap for Java objects
126                    created by the Java Virtual Machine in which jEdit is
127                    running. Add the command line option
128                    <userinput>-mxXXm</userinput> to the options passed to the
129                    version of the Java application loader you are using (such
130                    as <filename>java</filename>, <filename>java.exe</filename>
131                    or <filename>javaw.exe</filename>). In place of the
132                    <userinput>XX</userinput> in the option, use a multiple of
133                    16 between 32 and 256. If you already are using the option,
134                    increase the numeric portion of the
135                    <userinput>-mxXXm</userinput> parameter in increments of
136                    64.</para>
137                    <para>If you are using the <userinput>-jar</userinput>
138                    command line option with Java to run jEdit, remember that
139                    the <userinput>-jar</userinput> parameter must be the last
140                    Java option, followed immediately by the path to
141                    <filename>jedit.jar</filename> and then any jEdit command
142                    line options.</para>
143                    <para>If out of memory errors occur while running a build or
144                    compilation operation from within jEdit, you can also have
145                    the operation run in an external process rather than inside
146                    the same Java Virtual Machine running jEdit. The AntFarm
147                    plugin, for example, lets you select this approach as a
148                    configuration option. In other cases, you can run an
149                    external program using the command line interface of the
150                    Console plugin, which will capture and display the output of
151                    the external process and in many cases parse the output for
152                    error information.</para>
153                </answer>
154            </qandaentry>
155            <qandaentry>
156                <question id="textarea-corruption">
157                    <para>My textarea gets confused about the end of the buffer or in some other way corrupted (the characters are in the wrong place on the screen) every now and then. What
158                    should I do?</para>
159                </question>
160                <answer>
161                    <para>It happens to me sometimes too. I have this macro to work around it for now:
163/** Reset_TextArea.bsh */
167					Run this, and jEdit creates
168                    a new TextArea for you, and that one won't be confused. This
169                    can help avoid the need to restart jEdit. If you can
170                    reproduce the steps you took to cause this, please submit a
171                    bug report that details what plugins/versions you were
172                    using, and how to reproduce it. It may be specific to a file you are editing, or a particular combination of settings you are using, or sequence of actions you performed. </para>
173                </answer>
174            </qandaentry>
175            <qandaentry>
176                <question id="general-borders">
177                    <para>Why is jEdit's window movement and resizing so
178                    buggy?</para>
179                </question>
180                <answer>
181                    <para>Perhaps the option to let Java draw window borders is
182                    enabled. This option can lead to strange behavior on some
183                    Java versions and operating systems. Disable it in the
184                    <guilabel>Appearance</guilabel> tab of the
185                    <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global
186                    Options</guimenuitem> dialog box.</para>
187                </answer>
188            </qandaentry>
189            <qandaentry>
190                <question id="install-no-such-file">
191                    <para>What should I do when the installer displays the
192                    message, <screen>No such file or directory</screen>?</para>
193                </question>
194                <answer>
195                    <para>The full message that you may receive from the Java
196                    application launcher begins as follows: <screen>Exception in thread "main" No such file or directory
197...</screen> This means that the Java application launcher cannot read the jar
198                    archive file that you specified on the command line. If your
199                    Java runtime environment otherwise runs properly, then
200                    either you have named the incorrect file name or the
201                    installation file is corrupt or incomplete. Check the file
202                    name, download the installer again if necessary, and be sure
203                    to follow any specific instructions for your operating
204                    system posted on the <ulink url="">jEdit
205                    web site</ulink>.</para>
206                </answer>
207            </qandaentry>
208            <qandaentry>
209                <question id="install-noclassdef">
210                    <para>After downloading
211                    <filename>jeditXXXinstall.jar</filename> (the
212                    <filename>XXX</filename> represents the version number), I
213                    tried to run <userinput>java
214                    jeditXXXinstall.jar</userinput>, but got the error message,
215                    <screen>Exception in main(), NoClassDefFoundError: jeditXXXinstall/jar.</screen>
216                    What am I doing wrong?</para>
217                </question>
218                <answer>
219                    <para>You need to specify the <userinput>-jar</userinput>
220                    option for the Java application loader so that the loader
221                    will search the installation archive for the starting class
222                    file. Without the option, it treats the archive as a single
223                    class file (which it is not!), thus producing the error. The
224                    correct command line would be <userinput>java -jar
225                    jeditXXXinstall.jar</userinput>.</para>
226                </answer>
227            </qandaentry>
228            <qandaentry>
229                <question id="jedit-crashed">
230                    <para>jEdit crashed the JVM, what gives?</para>
231                </question>
232                <answer>
233                    <para>It's important to realise that java applications
234                    should never do this. The problem is almost certainly a bug
235                    in the JVM. Problems of this nature are often tricky to
236                    solve. Depending on your platform, there should be
237                    information logged about what caused the crash to occur. For
238                    Unix type systems you will likely get an error in the
239                    console (and for Mac OS X you may also get a report in
240                    ~/Library/Logs/CrashReporter/JavaApplicationStub.crash.log).
241					</para>
242                </answer>
243            </qandaentry>
244            <qandaentry>
245                <question id="general-slowstart">
246                    <para>Why is jEdit so slow to start up?</para>
247                </question>
248                <answer>
249                    <para>Some plugins require a lot of setup - chances are if
250                    you disable one, you will be able to determine the culprit.
251                    jEdit normally starts up quite quickly without
252                    plugins.</para>
253                    <procedure>
254                        <step>
255                            <para>To go the <guimenu>Utilities</guimenu> menu and
256                            select <guimenuitem>Activity
257                            Log</guimenuitem>.</para>
258                        </step>
259                        <step>
260                            <para>Scroll to the area where you see lines like
261                            <quote>[notice] JARClassLoader: Starting plugin
262                            XXX</quote>.</para>
263                        </step>
264                    </procedure>
265                    <para>You should be able to see which (if any) plugins are
266                    causing an excesively long delay.</para>
267                </answer>
268            </qandaentry>
269            <qandaentry>
270                <question id="general-slow">
271                    <para>Why is jEdit so slow?</para>
272                </question>
273                <answer>
274                    <para>There may be many causes for this. Java by nature is
275                    more demanding on hardware than native applications. Modern
276                    computers should not have much problem with this.</para>
277                    <para>The most likely cause is plugins that parse buffers or
278                    do other computationally expensive operations. These include
279                    XML, JavaSideKick, and CodeAid. If performance is important
280                    to you, installing a whole batch of plugins in one go is
281                    probably not a very good idea. Install them one at a time,
282                    so you can evaluate the effects of each. </para>
283                </answer>
284            </qandaentry>
285            <qandaentry>
286                <question id="general-docking">
287                    <para>Go to left/top/bottom/right docking area does not work
288                    for some plugins?</para>
289                </question>
290                <answer>
291                    <para>The plugin is missing a
292                    <methodname>requestDefaultFocus()</methodname> method.
293                    Plugin updates will be available from time to time, or you
294                    can email the author of the plugin to let them know of the
295                    problem.</para>
296                </answer>
297            </qandaentry>
298        </qandadiv>
299        <qandadiv id="unix-problems">
300            <title>Unix/Linux Problems</title>
301            <qandaentry>
302			    <question id="using-older-jre">
303				  <para>I'm trying to install jEdit on Linux, but I keep getting strange error messages.
304				  </para>
306Exception in thread "main" java.lang.UnsupportedClassVersionError:
307installer/Install (Unsupported major.minor version 49.0)
308Exception in thread "main" java.awt.AWTError: Cannot load AWT toolkit:
310				</question>
311				<answer>
312				 <para> Make sure the version of Java you are running is Sun Java 1.6 or higher.
313				 In debian/ubuntu,
314				 <literal> apt-get install sun-java6-jdk </literal>
315				 </para>
316		        </answer>
317				</qandaentry>
318		     <qandaentry>
319                <question id="install-jedit-home">
320                    <para>After installing jEdit on Linux, running the
321                    <userinput>jedit</userinput> command causes the error
322                    message: <screen>Warning: JAVA_HOME environment variable not set</screen>
323                    How can I fix this?</para>
324                </question>
325                <answer>
326                    <para>Your <filename>jedit</filename> shell script should be
327                    modified to set the <userinput>JAVA_HOME</userinput>
328                    variable to the directory containing the executables of your
329                    desired Java runtime environment (JRE).</para>
330                </answer>
331            </qandaentry>
332        </qandadiv>
333        <!--******************************************************** Windows -->
334        <qandadiv id="windows-problems">
335            <title>Windows Problems</title>
336            <qandaentry>
337                <question id="install-windows-errmessage">
338                    <para>When I try to run <filename>jedit.exe</filename> I get
339                    the message <screen>The JEditLauncher component does not appear to be installed.</screen></para>
340                </question>
341                <answer>
342                    <para>The dialog presenting this message asks if you would
343                    like to install the launcher. Select
344                    <userinput>Yes</userinput> and supply further information as
345                    prompted. A file named <filename>install.log</filename> is
346                    generated in the same directory as
347                    <filename>jedit.exe</filename> that contains information on
348                    the launcher's installation. You can send this file along
349                    with jEdit's Activity Log if you continue to have problems
350                    running jEdit with the launcher package.</para>
351                </answer>
352            </qandaentry>
353            <qandaentry>
354                <question id="install-error-regkey">
355                    <para>When I try to run the jEdit installation package in
356                    Windows, I get an error message, <screen>Error opening registration key
357				"software\javasoft\java runtime	environment".</screen> How can I fix
358                    this?</para>
359                </question>
360                <answer>
361                    <para>The problem is not with jEdit but may be caused by
362                    your installation of the Java runtime environment. Under
363                    Windows, Sun's Java application loader relies on entries in
364                    the Windows registry to find the files that create the
365                    runtime environment and a Java virtual machine. The loader
366                    (<filename>java.exe</filename>e or
367                    <filename>javaw.exe</filename>) is unable to find the
368                    necessary registration entry and therefore sends the error
369                    message. The best approach to fixing this is to uninstall
370                    and reinstall the JDK.</para>
371                </answer>
372            </qandaentry>
373            <qandaentry>
374                <question id="install-windows-badcommand">
375                    <para>When trying to install jEdit on Windows Me with an
376                    MS-DOS prompt, after entering <userinput>java -jar
377                    jeditXXXinstall.jar</userinput> I get the message
378                    <userinput>bad command or file name</userinput>. I have
379                    tried various alternatives but still cannot install.</para>
380                </question>
381                <answer>
382                    <para>You should confirm that you have a Java runtime
383                    environment installed, which will include
384                    <filename>java.exe</filename> and the version that omits a
385                    separate terminal window, <filename>javaw.exe</filename>.
386                    Make sure that the directory containing
387                    <filename>java.exe</filename> or
388                    <filename>javaw.exe</filename>is found in the value of your
389                    <filename>PATH</filename> environment variable. Otherwise
390                    you should give the full path to the chosen loader on your
391                    command line.</para>
392                </answer>
393            </qandaentry>
394            <qandaentry>
395                <question id="general-windows-ddraw">
396                    <para>When I run jEdit on Windows, it flashes, blinks, and
397                    doesn't display correctly! Why is your program so
398                    buggy?</para>
399                </question>
400                <answer>
401                    <para>A frequent cause of this problem is buggy video
402                    drivers and/or a buggy DirectDraw implementation. A
403                    workaround is to disable Java's use of DirectDraw by adding
404                    the following option to the Java virtual machine command
405                    line:</para>
406                    <programlisting>-Dsun.java2d.noddraw=true</programlisting>
407                </answer>
408            </qandaentry>
409        </qandadiv>
410    </qandaset>