some dynamic flags cannot be used with OPTIONS_GHC, e.g. -i, -package

[ghc-hetmet.git] / docs / users_guide / ghci.xml

diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml
index e722739..5f38b37 100644 (file)
--- a/docs/users_guide/ghci.xml
+++ b/docs/users_guide/ghci.xml
@@ -906,7 +906,7 @@ $ ghci -lm
 
       <varlistentry>
        <term>
-          <literal>:breakpoint</literal> <replaceable>list|add|del|stop|step</replaceable> ...
+          <literal>:breakpoint</literal> <replaceable>list|add|continue|del|stop|step</replaceable> ...
           <indexterm><primary><literal>:breakpoint</literal></primary></indexterm>
         </term>
        <listitem>
@@ -963,6 +963,15 @@ $ ghci -lm
 
       <varlistentry>
        <term>
+          <literal>:continue</literal> 
+          <indexterm><primary><literal>:continue</literal></primary></indexterm>
+        </term>
+       <listitem> Shortcut to <literal>:breakpoint continue </literal>
+       </listitem>
+      </varlistentry>
+
+      <varlistentry>
+       <term>
           <literal>:def</literal> <replaceable>name</replaceable> <replaceable>expr</replaceable>
           <indexterm><primary><literal>:def</literal></primary></indexterm>
         </term>
@@ -1551,12 +1560,12 @@ Prelude> :set -fno-glasgow-exts
           </para></listitem>
        </itemizedlist></para>
     <sect2><title>Using the debugger</title>
-    <para>The debugger allows the insertion of breakpoints at specific locations in the source code. These locations are goberned by event sites, and not by line as in traditional debuggers such as gdb. </para> <para>
+    <para>The debugger allows the insertion of breakpoints at specific locations in the source code. These locations are governed by event sites, and not by line as in traditional debuggers such as gdb. </para> <para>
       Once a breakpointed event is hit, the debugger stops the execution and you can examine the local variables in scope
       in the context of the event, as well as evaluate arbitrary Haskell expressions in
       a special interactive prompt. </para><para>
       
-     When you are done you issue the <literal>:quit</literal> 
+     When you are done you issue the <literal>:continue</literal> 
       command to leave the breakpoint and let the execution go on. 
      Note that not all the GHCi commands are supported in a breakpoint. 
 
@@ -1706,6 +1715,26 @@ x :: Int
     at line <literal>line</literal> in <literal>module</literal>, if any.
   </para></listitem>
 </varlistentry>
+
+<varlistentry>
+  <term>
+    <literal>:breakpoint continue</literal>
+  </term>
+  <listitem><para>
+   When at a breakpoint, continue execution up to the next breakpoint
+   or end of evaluation.
+  </para></listitem>
+</varlistentry>
+
+<varlistentry>
+  <term>
+    <literal>:continue</literal>
+  </term>
+  <listitem><para>
+      Shortcut for <literal>:breakpoint continue</literal>
+  </para></listitem>
+</varlistentry>
+
 <varlistentry>
   <term>
     <literal>:breakpoint list</literal>