PageRenderTime 36ms CodeModel.GetById 11ms RepoModel.GetById 0ms app.codeStats 0ms

/jEdit/tags/jedit-4-5-pre1/doc/users-guide/activity-log.xml

#
XML | 61 lines | 46 code | 12 blank | 3 comment | 0 complexity | 9b0be62dda90e4124692ae0ef1af5f9e 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. <?xml version="1.0" encoding="UTF-8"?>
  2. <appendix id="activity-log">
  3. <!-- jEdit buffer-local properties: -->
  4. <!-- :indentSize=4:noTabs=true: -->
  5. <!-- :xml.root=users-guide.xml: -->
  6. <title>The Activity Log</title>
  7. <para>The <firstterm>activity log</firstterm> is very useful for
  8. troubleshooting problems, and helps when developing plugins.</para>
  9. <para><guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Activity
  10. Log</guimenuitem> displays the last 500 lines of the activity log. By
  11. default, the activity log is shown in a floating window. This window can be
  12. docked using the commands in its top-left corner popup menu; see <xref
  13. linkend="docking" />.</para>
  14. <para>The complete log can be found in the <filename>activity.log</filename>
  15. file inside the jEdit settings directory, the path of which is shown inside
  16. the activity log window.</para>
  17. <para>jEdit writes the following information to the activity log:</para>
  18. <itemizedlist>
  19. <listitem>
  20. <para>Information about your Java implementation (version, operating
  21. system, architecture, etc).</para>
  22. </listitem>
  23. <listitem>
  24. <para>All error messages and runtime exceptions (most errors are
  25. shown in dialog boxes as well, but the activity log usually contains
  26. more detailed and technical information).</para>
  27. </listitem>
  28. <listitem>
  29. <para>All sorts of debugging information that can be helpful when
  30. tracking down bugs.</para>
  31. </listitem>
  32. <listitem>
  33. <para>Information about loaded plugins.</para>
  34. </listitem>
  35. </itemizedlist>
  36. <para>While jEdit is running, the log file on disk may not always accurately
  37. reflect what has been logged, due to buffering being done for performance
  38. reasons. To ensure the file on disk is up to date, invoke the
  39. <guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Update
  40. Activity Log on Disk</guimenuitem> command. The log file is also
  41. automatically updated on disk when jEdit exits.</para>
  42. <para>
  43. The "Settings" button in the Activity Log window shows a dialog that lets
  44. you adjust the output colors, filter the messages by type, and lets you set
  45. the maximum number of lines to display. Note that larger numbers will
  46. decrease the overall performance of jEdit since these lines are kept in
  47. memory.
  48. </para>
  49. </appendix>