PageRenderTime 41ms CodeModel.GetById 37ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/jEdit/tags/jedit-4-2-pre14/doc/users-guide/activity-log.xml

#
XML | 44 lines | 40 code | 1 blank | 3 comment | 0 complexity | 1768173e1a44ffc612d3293e6769fdc6 MD5 | raw file
 1<!-- jEdit buffer-local properties: -->
 2<!-- :indentSize=1:noTabs=true: -->
 3<!-- :xml.root=users-guide.xml: -->
 4
 5<appendix id="activity-log"><title>The Activity Log</title>
 6 <para>
 7  The <firstterm>activity log</firstterm> is very useful for
 8  troubleshooting problems, and helps when developing plugins.
 9 </para>
10 <para>
11  <guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Activity
12  Log</guimenuitem> displays
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 </para>
15 <para>
16  The complete
17  log can be found in the <filename>activity.log</filename> file inside the
18  jEdit settings directory, the path of which is shown inside the activity
19  log window.
20 </para>
21 <para>
22  jEdit writes the following information to the activity log:
23 </para>
24 <itemizedlist>
25  <listitem><para>Information about your Java implementation (version,
26  operating system, architecture, etc).</para></listitem>
27  <listitem><para>All error messages and runtime exceptions (most errors
28  are shown in dialog boxes as well, but the activity log usually
29  contains more detailed and technical information).
30  </para></listitem>
31  <listitem><para>All sorts of debugging information that can be helpful
32  when tracking down bugs.</para></listitem>
33  <listitem><para>Information about loaded plugins.</para></listitem>
34 </itemizedlist>
35 <para>
36  While jEdit is running, the log file on disk may not always accurately reflect
37  what has been logged, due to buffering being done for performance reasons.
38  To ensure the file on disk is up to
39  date, invoke the
40  <guimenu>Utilities</guimenu>&gt;<guisubmenu>Troubleshooting</guisubmenu>&gt;<guimenuitem>Update
41  Activity Log on Disk</guimenuitem> command. The log file is also automatically
42  updated on disk when jEdit exits.
43 </para>
44</appendix>