PageRenderTime 29ms CodeModel.GetById 4ms RepoModel.GetById 0ms app.codeStats 0ms

/www/tags/NOV_07_2009/htdocs/42docs/users-guide/activity-log.xml.bak

#
Unknown | 44 lines | 43 code | 1 blank | 0 comment | 0 complexity | 1768173e1a44ffc612d3293e6769fdc6 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. 

  2. <!-- :indentSize=1:noTabs=true: -->
    3. 

  3. <!-- :xml.root=users-guide.xml: -->
    4. 

  4. 

  5. <appendix id="activity-log"><title>The Activity Log</title>
    6. 

  6.  <para>
    7. 

  7.   The <firstterm>activity log</firstterm> is very useful for
    8. 

  8.   troubleshooting problems, and helps when developing plugins.
    9. 

  9.  </para>
    10. 

  10.  <para>
    11. 

  11.   <guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Activity
    12. 

  12.   Log</guimenuitem> displays
    13. 

  13.   the last 500 lines of the activity log. By default, the activity log is shown in a floating window. This window can be docked using the commands in its top-left corner popup menu; see <xref linkend="docking" />.
    14. 

  14.  </para>
    15. 

  15.  <para>
    16. 

  16.   The complete
    17. 

  17.   log can be found in the <filename>activity.log</filename> file inside the
    18. 

  18.   jEdit settings directory, the path of which is shown inside the activity
    19. 

  19.   log window.
    20. 

  20.  </para>
    21. 

  21.  <para>
    22. 

  22.   jEdit writes the following information to the activity log:
    23. 

  23.  </para>
    24. 

  24.  <itemizedlist>
    25. 

  25.   <listitem><para>Information about your Java implementation (version,
    26. 

  26.   operating system, architecture, etc).</para></listitem>
    27. 

  27.   <listitem><para>All error messages and runtime exceptions (most errors
    28. 

  28.   are shown in dialog boxes as well, but the activity log usually
    29. 

  29.   contains more detailed and technical information).
    30. 

  30.   </para></listitem>
    31. 

  31.   <listitem><para>All sorts of debugging information that can be helpful
    32. 

  32.   when tracking down bugs.</para></listitem>
    33. 

  33.   <listitem><para>Information about loaded plugins.</para></listitem>
    34. 

  34.  </itemizedlist>
    35. 

  35.  <para>
    36. 

  36.   While jEdit is running, the log file on disk may not always accurately reflect
    37. 

  37.   what has been logged, due to buffering being done for performance reasons.
    38. 

  38.   To ensure the file on disk is up to
    39. 

  39.   date, invoke the
    40. 

  40.   <guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Update
    41. 

  41.   Activity Log on Disk</guimenuitem> command. The log file is also automatically
    42. 

  42.   updated on disk when jEdit exits.
    43. 

  43.  </para>
    44. 

  44. </appendix>
    45. 

  45.