PageRenderTime 52ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 0ms


XML | 495 lines | 459 code | 28 blank | 8 comment | 0 complexity | be5e06c2dfce8eb647a53a2f8598fc15 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
  1. <!-- jEdit buffer-local properties: -->
  2. <!-- :indentSize=4:noTabs=false:maxLineLen=72:tabSize=4: -->
  3. <!-- :xml.root=faq.xml: -->
  4. <!-- jEdit FAQ -->
  5. <!-- Copyright (C) 2003 John Gellene, Kris Kopicki -->
  6. <sect1 id="problems"><title>Problems</title>
  7. <para>
  8. This section deals with problems you may experience while using or
  9. installing jEdit. Problems that aren't OS specific are listed under
  10. <link linkend="general-problems"><quote>General Problems</quote></link>.
  11. </para>
  12. <qandaset defaultlabel="qanda">
  13. <qandadiv id="general-problems">
  14. <title>General Problems</title>
  15. <qandaentry>
  16. <question id="wont-start"><para>
  17. jEdit won't start. What should I do?
  18. </para></question>
  19. <answer><para>
  20. If you don't have a clue as to why you cannot run jEdit, it's
  21. best to perform a step-by-step diagnosis. Begin by finding the
  22. Java application loader you are using: <filename>java.exe</filename>,
  23. <filename>javaw.exe</filename> or <filename>java</filename>. Make sure
  24. it is running by entering its full path with the <userinput>-h</userinput>
  25. parameter in a terminal or console window. If you can't find
  26. the Java application loader, your Java runtime environment package
  27. may be missing or incomplete.
  28. </para>
  29. <para>
  30. Next, find where you have installed jEdit. You should look
  31. for the file <filename>jedit.jar</filename> which contains all
  32. of the application's Java class files in a compressed archive.
  33. </para>
  34. <para>
  35. Once you have both files, run the Java loader with the
  36. <userinput>-jar</userinput> option and with
  37. <filename>jedit.jar</filename> as the target. Make sure that
  38. you either specify full paths for both files or that the
  39. directories for the files are part of your <filename>PATH</filename>
  40. environment variable. If jEdit does not load at this point, the likely
  41. problem is a corrupt <filename>jedit.jar</filename> file. Try
  42. downloading the application again.
  43. </para>
  44. <para>
  45. If jEdit does load using this procedure, you need to examine
  46. the <quote>shortcut</quote> loading mechanism you wish to use.
  47. </para>
  48. <para>
  49. On Linux and MacOS X, you need to find and examine the <filename>jedit</filename>
  50. shell script provided by the installation routine to confirm that the
  51. script's commands target the correct files and locations, and that
  52. variables like <filename>JAVA_HOME</filename> are either defined in the
  53. script or elsewhere in your shell's environment. Don't forget to make
  54. sure that the script's file permissions allow you to execute it as a shell script.
  55. </para>
  56. <para>
  57. On Windows, if you are using a batch script to run jEdit, the
  58. same points (other than file permissions) apply to examining
  59. <filename>jedit.bat</filename>. If you are using
  60. jEditLauncher, run <userinput>jedit /p</userinput> in jEdit's
  61. installation directory from a command line to get the custom
  62. loader's setup dialog. Here you can check the paths for both
  63. the Java application loader and jEdit as well as any command
  64. line parameters for both programs. Make sure that you have
  65. placed Java and jEdit options in the correct input fields.
  66. If the parameters seems correct
  67. but jEdit will not load with the Windows launcher, try
  68. uninstalling and reinstalling the launcher by running
  69. <userinput>jedit /u</userinput> followed by
  70. <userinput>jedit /i</userinput>.
  71. </para>
  72. <para>
  73. If at this point you're still stuck, ask for help on the
  74. jedit-users mailing list, the jEdit Community
  75. <quote>Installation</quote> message board or on IRC.
  76. You're bound to find someone quickly.
  77. </para>
  78. </answer>
  79. </qandaentry>
  80. <qandaentry>
  81. <question id="start-missing-plugins"><para>
  82. After jEdit starts, I can't see all of the plugins I have downloaded.
  83. How can I make them appear?
  84. </para></question>
  85. <answer><para>
  86. If you use jEdit's Plugin Manager to download and install plugins, your
  87. plugins will be found in the <filename>jars</filename> subdirectory of
  88. one of two directories: either the directory in which jEdit is
  89. installed, or the current user's settings directory. These are the only
  90. location jEdit examines when it loads plugins at startup.
  91. </para>
  92. <para>
  93. The default location of the settings directory depends on your operating
  94. system. You can find out its location during a jEdit session by
  95. evaluating <userinput>jedit.getSettingsDirectory()</userinput> in BeanShell.
  96. </para>
  97. <para>
  98. The settings directory can be changed by using the
  99. <userinput>-settings</userinput> command line parameter. If you change the
  100. location of the settings directory with this parameter, jEdit will not
  101. be able to find plugin archive files in the old location.
  102. If you use or change the <userinput>-settings</userinput>
  103. parameter, make sure your plugins don't get left behind.
  104. </para>
  105. </answer>
  106. </qandaentry>
  107. <qandaentry>
  108. <question id="problems-out-of-memory"><para>
  109. During an editing session I get an error message about an
  110. <quote>OutOfMemoryError</quote> while working with a large file or
  111. performing a lengthy operation. The message reappears every time
  112. I retry the operation. How can I prevent this?
  113. </para></question>
  114. <answer><para>
  115. One solution that often works is to set or increase the allocation of
  116. memory to the heap for Java objects created by the Java Virtual Machine
  117. in which jEdit is running. Add the command line option
  118. <userinput>-mxXXm</userinput> to the options passed to the version of
  119. the Java application loader you are using (such as
  120. <filename>java</filename>, <filename>java.exe</filename> or
  121. <filename>javaw.exe</filename>). In place of the
  122. <userinput>XX</userinput> in the option, use a multiple of 16
  123. between 32 and 128. If you already are using the option, increase the
  124. numeric portion of the <userinput>-mxXXm</userinput> parameter in
  125. increments of 16. Many users have good results using 48 or 64, but you
  126. should try different values for the best result on your installation.
  127. </para>
  128. <para>
  129. If you are using the <userinput>-jar</userinput> command line option
  130. with Java to run jEdit, remember that the <userinput>-jar</userinput>
  131. parameter must be the last Java option, followed immediately by the path
  132. to <filename>jedit.jar</filename> and then any jEdit command line options.
  133. </para>
  134. <para>
  135. If out of memory errors occur while running a build or compilation
  136. operation from within jEdit, you can also have the operation run in an
  137. external process rather than inside the same Java Virtual Machine
  138. running jEdit. The AntFarm plugin, for example, lets you select this
  139. approach as a configuration option. In other cases, you can run an
  140. external program using the command line interface of the Console plugin,
  141. which will capture and display the output of the external process and in
  142. many cases parse the output for error information.
  143. </para></answer>
  144. </qandaentry>
  145. <qandaentry>
  146. <question id="install-no-such-file"><para>
  147. What should I do when the installer displays the message,
  148. <screen>No such file or directory</screen>?
  149. </para></question>
  150. <answer><para>
  151. The full message that you may receive from the Java application launcher
  152. begins as follows:
  153. <screen>Exception in thread "main" No such file or directory
  154. ...</screen>
  155. This means that the Java application launcher cannot read the
  156. jar archive file that you specified on the command line. If your Java
  157. runtime environment otherwise runs properly, then either you have named
  158. the incorrect file name or the installation file is corrupt or
  159. incomplete. Check the file name, download the installer again if
  160. necessary, and be sure to follow any specific instructions for your
  161. operating system posted on the <ulink
  162. url="">jEdit web site</ulink>.
  163. </para></answer>
  164. </qandaentry>
  165. <qandaentry>
  166. <question id="install-noclassdef">
  167. <para>
  168. After downloading <filename>jeditXXXinstall.jar</filename> (the
  169. <filename>XXX</filename> represents the version number), I tried to run
  170. <userinput>java jeditXXXinstall.jar</userinput>, but got the error message,
  171. <screen>Exception in main(), NoClassDefFoundError: jeditXXXinstall/jar.</screen> What am I doing wrong?
  172. </para>
  173. </question>
  174. <answer>
  175. <para>
  176. You need to specify the <userinput>-jar</userinput> option for the Java
  177. application loader so that the loader will search the installation archive
  178. for the starting class file. Without the option, it treats the archive as a
  179. single class file (which it is not!), thus producing the error. The correct
  180. command line would be <userinput>java -jar jeditXXXinstall.jar</userinput>.
  181. </para>
  182. </answer>
  183. </qandaentry>
  184. <qandaentry>
  185. <question id="jedit-crashed">
  186. <para>
  187. jEdit crashed the JVM, what gives?
  188. </para>
  189. </question>
  190. <answer>
  191. <para>
  192. It's important to realise that java applications should never do this.
  193. The problem is almost certainly a bug in the JVM. Problems of this
  194. nature are often tricky to solve. Depending on your platform, there
  195. should be information logged about what caused the crash to occur. For
  196. Unix type systems you will likely get an error in the console (and for
  197. Mac OS X you may also get a report in ~/Library/Logs/CrashReporter/JavaApplicationStub.crash.log).
  198. Some recent problems with Java 1.4.x and Windows were the result of a
  199. bug in the JVM and certain graphics card drivers.
  200. </para>
  201. </answer>
  202. </qandaentry>
  203. <qandaentry>
  204. <question id="general-slowstart">
  205. <para>
  206. Why is jEdit so slow to start up?
  207. </para>
  208. </question>
  209. <answer>
  210. <para>
  211. The most likely cause is one or more plugins that are installed. jEdit 4.1
  212. displays loading times for plugins in the activity log.
  213. </para>
  214. <procedure>
  215. <step>
  216. <para>
  217. To go the <guimenu>Utilities</guimenu> menu and select <guimenuitem>Activity Log</guimenuitem>.
  218. </para>
  219. </step>
  220. <step>
  221. <para>
  222. Scroll to the area where you see lines like <quote>[notice] JARClassLoader: Starting plugin XXX</quote>.
  223. </para>
  224. </step>
  225. </procedure>
  226. <para>
  227. You should be able to see which (if any) plugins are causing an excesively long delay.
  228. </para>
  229. </answer>
  230. </qandaentry>
  231. <qandaentry>
  232. <question id="general-slow">
  233. <para>
  234. Why is jEdit so slow?
  235. </para>
  236. </question>
  237. <answer>
  238. <para>
  239. There may be many causes for this. Java by nature is more demanding on hardware than native
  240. applications. Modern computers should not have much problem with this.
  241. </para>
  242. <para>
  243. The most likely cause is plugins that parse buffers or do other computationally expensive
  244. operations. These include XML, SpeedJava and CodeAid. If performance is important to you, installing
  245. a whole batch of plugins in one go is probably not a very good idea. Install them one at a time,
  246. so you can evaluate the effects of each.
  247. <note>
  248. <para>
  249. If you are experiencing slow downs when switching and saving buffers (up to 20 second delays) and you
  250. have the TaskList plugin installed, check that the version is greater than 0.4. Versions after 0.4 fix
  251. the problem.
  252. </para>
  253. </note>
  254. </para>
  255. </answer>
  256. </qandaentry>
  257. <qandaentry>
  258. <question id="general-docking">
  259. <para>
  260. Go to left/top/bottom/right docking area does not work for some plugins?
  261. </para>
  262. </question>
  263. <answer>
  264. <para>
  265. The plugin is missing a <methodname>requestDefaultFocus()</methodname> method.
  266. Plugin updates will be available from time to time, or you can email the author
  267. of the plugin to let them know of the problem.
  268. </para>
  269. </answer>
  270. </qandaentry>
  271. </qandadiv>
  272. <!--********************************************************* Mac OS -->
  273. <qandadiv id="macos-problems">
  274. <title>Mac OS Problems</title>
  275. <qandaentry>
  276. <question id="blurry-tabs">
  277. <para>
  278. Why are the tabs for docked windows blurry under OS X 10.2?
  279. </para>
  280. </question>
  281. <answer>
  282. <para>
  283. In Mac OS X 10.2 Apple enabled Hardware Acceleration for Java by default.
  284. Unfortunately it had some bugs. This is the result of one of these bugs.
  285. The only way to avoid this problem is to disable hardware acceleration for
  286. jEdit or your whole system.
  287. To disable it in jEdit you will need to edit
  288. the following file:
  289. jEdit/
  290. You will need to add the line <userinput></userinput>.
  291. This is done for you in the Mac OS X package of jEdit 4.1.
  292. </para>
  293. </answer>
  294. </qandaentry>
  295. <qandaentry>
  296. <question id="not-in-menubar">
  297. <para>
  298. Why are the menus not in the menubar?
  299. </para>
  300. </question>
  301. <answer>
  302. <para>
  303. You can enable the use of OS X's menubar in the Mac OS Plugin settings.
  304. You should note that the reason this is off by default is because of numerous
  305. problems with using the Mac OS X menubar. For example dynamic menus, shortcuts
  306. and check box menu items do not work correctly or at all. All bar the shortcut
  307. issue is resolved in Java 1.4.1 (currently in beta).
  308. </para>
  309. </answer>
  310. </qandaentry>
  311. <qandaentry>
  312. <question id="freeze-hide">
  313. <para>
  314. Why does jEdit freeze when I hide the application while it is starting up?
  315. </para>
  316. </question>
  317. <answer>
  318. <para>
  319. This appears to be a bug in Java 1.3.1. Once the splash screen has gone
  320. it should be safe to hide the application.
  321. </para>
  322. </answer>
  323. </qandaentry>
  324. <qandaentry>
  325. <question id="freeze-general">
  326. <para>
  327. Why does jEdit freeze my whole system?
  328. </para>
  329. </question>
  330. <answer>
  331. <para>
  332. Under some hardware configurations this can happen. It is only known to happen
  333. with Rage 128 Pro graphics cards. There appears to be a bug relating to the graphics
  334. card drivers that cause any carbon applications using the card to freeze. Since java
  335. 1.3.1 is carbon based, it suffers from this problem. Follow the instructions
  336. <link linkend="blurry-tabs">here</link> to disable hardware acceleration. Java 1.4.x
  337. does not suffer from this problem (in beta at this time).
  338. </para>
  339. </answer>
  340. </qandaentry>
  341. </qandadiv>
  342. <!--***************************************************** Unix/Linux -->
  343. <qandadiv id="unix-problems">
  344. <title>Unix/Linux Problems</title>
  345. <qandaentry>
  346. <question id="install-jedit-home">
  347. <para>
  348. After installing jEdit on Linux, running the <userinput>jedit</userinput>
  349. command causes the error message:
  350. <screen>Warning: JAVA_HOME environment variable not set</screen>
  351. How can I fix this?
  352. </para>
  353. </question>
  354. <answer>
  355. <para>
  356. Your <filename>jedit</filename> shell script should
  357. be modified to set the <userinput>JAVA_HOME</userinput> variable
  358. to the directory containing the executables of
  359. your desired Java runtime environment (JRE).
  360. </para>
  361. </answer>
  362. </qandaentry>
  363. <qandaentry>
  364. <question id="install-mandrake-kaffe">
  365. <para>
  366. How can I get jEdit to run on Mandrake Linux 8.1? When I try to start the
  367. program, I keep getting an error which begins as follows:
  368. <screen>java/lang/NoClassDefFoundError: Ljavax/swing/text/Document; at
  369. java.lang.reflect.Method.invoke( at
  370. kaffe.jar.ExecJarName.main</screen>
  371. </para>
  372. </question>
  373. <answer>
  374. <para>
  375. This version of Mandrake Linux uses the Open Source Kaffe package as its default
  376. Java virtual machine. Kaffe is compliant with version 1.1 (and to a limited extent,
  377. version 1.2) of the Java platform. However, the latest version of jEdit, version 4.1, requires
  378. at least version 1.3. You will need to install another Java package for Linux
  379. (either Blackdown, IBM or Sun) that complies with at least version 1.3.
  380. </para>
  381. </answer>
  382. </qandaentry>
  383. <qandaentry>
  384. <question id="install-linux-keyboard">
  385. <para>
  386. I installed jEdit 3.2.2 from the RPM on Mandrake 8.1 and I am unable to send any
  387. keyboard inputs to jEdit. But the mouse interacts with the program just fine. I
  388. have tried running it on Sun's JDK 1.3.1 and Blackdown's latest JDK (Dec. 2001)
  389. without any luck.
  390. </para>
  391. </question>
  392. <answer>
  393. <para>
  394. This problem has been reported with various combinations of window managers and
  395. desktop environments. The IBM JDK has not been reported to have this problem. In
  396. addition, there have not been reported problems with the Sun and Blackdown JDK's
  397. when running under the Sawfish window manager.
  398. </para>
  399. </answer>
  400. </qandaentry>
  401. </qandadiv>
  402. <!--******************************************************** Windows -->
  403. <qandadiv id="windows-problems">
  404. <title>Windows Problems</title>
  405. <qandaentry>
  406. <question id="install-windows-errmessage">
  407. <para>
  408. When I try to run
  409. <filename>jedit.exe</filename> I get the message
  410. <screen>The JEditLauncher component does not appear to be installed.</screen>
  411. </para>
  412. </question>
  413. <answer>
  414. <para>
  415. The dialog presenting this message asks if you would like to install the
  416. launcher. Select <userinput>Yes</userinput> and supply further information
  417. as prompted. A file named <filename>install.log</filename> is generated in the
  418. same directory as <filename>jedit.exe</filename> that
  419. contains information on the launcher's installation. You can send this file
  420. along with jEdit's Activity Log if you continue to have problems running jEdit
  421. with the launcher package.
  422. </para>
  423. </answer>
  424. </qandaentry>
  425. <qandaentry>
  426. <question id="install-error-regkey">
  427. <para>
  428. When I try to run the jEdit installation package in Windows, I get an error
  429. message, <screen>Error opening registration key
  430. "software\javasoft\java runtime environment".</screen> How can I fix this?
  431. </para>
  432. </question>
  433. <answer>
  434. <para>
  435. The problem is not with jEdit but may be caused by your installation of the Java
  436. runtime environment. Under Windows, Sun's Java application loader relies on
  437. entries in the Windows registry to find the files that create the runtime
  438. environment and a Java virtual machine. The loader (<filename>java.exe</filename>e or
  439. <filename>javaw.exe</filename>) is
  440. unable to find the necessary registration entry and therefore sends the error
  441. message. The best approach to fixing this is to uninstall and reinstall the JDK.
  442. </para>
  443. </answer>
  444. </qandaentry>
  445. <qandaentry>
  446. <question id="install-windows-badcommand">
  447. <para>
  448. When trying to install jEdit on Windows Me with an MS-DOS prompt, after entering
  449. <userinput>java -jar jeditXXXinstall.jar</userinput> I get the message
  450. <userinput>bad command or file name</userinput>.
  451. I have tried various alternatives but still cannot install.
  452. </para>
  453. </question>
  454. <answer>
  455. <para>
  456. You should confirm that you have a Java runtime environment installed, which
  457. will include <filename>java.exe</filename> and the version that omits a separate
  458. terminal window, <filename>javaw.exe</filename>. Make sure that the directory
  459. containing <filename>java.exe</filename> or <filename>javaw.exe</filename>is found
  460. in the value of your <filename>PATH</filename> environment variable.
  461. Otherwise you should give the full path to the chosen loader on your command line.
  462. </para>
  463. </answer>
  464. </qandaentry>
  465. </qandadiv>
  466. </qandaset>
  467. </sect1>