PageRenderTime 47ms CodeModel.GetById 38ms app.highlight 5ms RepoModel.GetById 1ms app.codeStats 0ms

/www/tags/NOV_07_2009/htdocs/users-guide/activity-log.html

#
HTML | 16 lines | 16 code | 0 blank | 0 comment | 0 complexity | 2d431c08f31e21d28738df4fa5d755d1 MD5 | raw file
 1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix B. The Activity Log</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="jEdit 4.3 User's Guide"><link rel="up" href="using-jedit-part.html" title="Part I. Using jEdit"><link rel="prev" href="shortcuts.html" title="Appendix A. Keyboard Shortcuts"><link rel="next" href="history.html" title="Appendix C. History Text Fields"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix B. The Activity Log</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="shortcuts.html">Prev</a> </td><th width="60%" align="center">Part I. Using jEdit</th><td width="20%" align="right"> <a accesskey="n" href="history.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="activity-log"></a>Appendix B. The Activity Log</h2></div></div></div><p>The <em class="firstterm">activity log</em> is very useful for
 2    troubleshooting problems, and helps when developing plugins.</p><p><span class="guimenu"><strong>Utilities</strong></span>&gt;<span class="guisubmenu"><strong>Troubleshooting</strong></span>&gt;<span class="guimenuitem"><strong>Activity
 3    Log</strong></span> displays the last 500 lines of the activity log. By
 4    default, the activity log is shown in a floating window. This window can be
 5    docked using the commands in its top-left corner popup menu; see <a class="xref" href="docking.html" title="Window Docking">the section called &#8220;Window Docking&#8221;</a>.</p><p>The complete log can be found in the <code class="filename">activity.log</code>
 6    file inside the jEdit settings directory, the path of which is shown inside
 7    the activity log window.</p><p>jEdit writes the following information to the activity log:</p><div class="itemizedlist"><ul type="disc"><li><p>Information about your Java implementation (version, operating
 8            system, architecture, etc).</p></li><li><p>All error messages and runtime exceptions (most errors are
 9            shown in dialog boxes as well, but the activity log usually contains
10            more detailed and technical information).</p></li><li><p>All sorts of debugging information that can be helpful when
11            tracking down bugs.</p></li><li><p>Information about loaded plugins.</p></li></ul></div><p>While jEdit is running, the log file on disk may not always accurately
12    reflect what has been logged, due to buffering being done for performance
13    reasons. To ensure the file on disk is up to date, invoke the
14    <span class="guimenu"><strong>Utilities</strong></span>&gt;<span class="guisubmenu"><strong>Troubleshooting</strong></span>&gt;<span class="guimenuitem"><strong>Update
15    Activity Log on Disk</strong></span> command. The log file is also
16    automatically updated on disk when jEdit exits.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="shortcuts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using-jedit-part.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="history.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Keyboard Shortcuts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. History Text Fields</td></tr></table></div></body></html>