PageRenderTime 18ms CodeModel.GetById 11ms app.highlight 4ms RepoModel.GetById 1ms app.codeStats 0ms


HTML | 28 lines | 28 code | 0 blank | 0 comment | 0 complexity | 48b99cb3576634513f3db9137bfd583c 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.65.1"><link rel="home" href="index.html" title="jEdit 4.2 User's Guide"><link rel="up" href="using-jedit-part.html" title="Part I. Using jEdit"><link rel="previous" 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></div></div><p>
 2  The <i class="firstterm">activity log</i> is very useful for
 3  troubleshooting problems, and helps when developing plugins.
 4 </p><p>
 5  <span><b class="guimenu">Utilities</b></span>&gt;<span><b class="guisubmenu">Troubleshooting</b></span>&gt;<span><b class="guimenuitem">Activity
 6  Log</b></span> displays
 7  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 <a href="docking.html" title="Window Docking">the section called &#8220;Window Docking&#8221;</a>.
 8 </p><p>
 9  The complete
10  log can be found in the <tt class="filename">activity.log</tt> file inside the
11  jEdit settings directory, the path of which is shown inside the activity
12  log window.
13 </p><p>
14  jEdit writes the following information to the activity log:
15 </p><div class="itemizedlist"><ul type="disc"><li><p>Information about your Java implementation (version,
16  operating system, architecture, etc).</p></li><li><p>All error messages and runtime exceptions (most errors
17  are shown in dialog boxes as well, but the activity log usually
18  contains more detailed and technical information).
19  </p></li><li><p>All sorts of debugging information that can be helpful
20  when tracking down bugs.</p></li><li><p>Information about loaded plugins.</p></li></ul></div><p>
21  While jEdit is running, the log file on disk may not always accurately reflect
22  what has been logged, due to buffering being done for performance reasons.
23  To ensure the file on disk is up to
24  date, invoke the
25  <span><b class="guimenu">Utilities</b></span>&gt;<span><b class="guisubmenu">Troubleshooting</b></span>&gt;<span><b class="guimenuitem">Update
26  Activity Log on Disk</b></span> command. The log file is also automatically
27  updated on disk when jEdit exits.
28 </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>