[nemiver/mallard-docs: 8/28] Add documentation for session

[Baptiste Mille-Mathias <baptistem src gnome org>]

commit 190ed8cc5469a31b5b8b027cdeb7c2a78ffa319e
Author: Baptiste Mille-Mathias <baptiste millemathias gmail com>
Date:   Mon Apr 29 22:14:09 2013 +0200

    Add documentation for session

 help/C/load-session.page |   29 +++++++++++++++++++++++++++++
 help/C/save-session.page |   30 ++++++++++++++++++++++++++++++
 2 files changed, 59 insertions(+), 0 deletions(-)
---
diff --git a/help/C/load-session.page b/help/C/load-session.page
new file mode 100644
index 0000000..078cac3
--- /dev/null
+++ b/help/C/load-session.page
@@ -0,0 +1,29 @@
+<page xmlns="http://projectmallard.org/1.0/";
+      type="topic"
+      id="load-session">
+
+    <info>
+        <link type="guide" xref="index#session"/>
+        <revision version="0.1" date="2013-04-29" status="stub"/>
+        <desc>How to load a Nemiver session</desc>
+    </info>
+
+    <title>Load a debugging session</title>
+
+    <p><guiseq><gui style="menu">File</gui><gui style="menuitem">Resume Saved 
+    Session…</gui></guiseq> to display the list of saved session.
+    Select the session in the list, where each entry is named <var>application
+    name</var>-<var>yyyy-mm-dd hh:mm:ss</var>, then choose <gui>Execute</gui>.
+    </p>
+
+    <p><app>Nemiver</app> then start the application, and restart the debugging
+    session, where you stopped it previously.</p>
+
+    <section>
+        <title>Load a session from command line</title>
+        <p>You can start a debugging session from the command line, 
+        <cmd>nemiver --session</cmd><var>$id</var> where <var>$id</var> is the
+        identifier of the session you want to load, as listed in the session 
+        interface.</p>
+    </section>
+</page>
diff --git a/help/C/save-session.page b/help/C/save-session.page
new file mode 100644
index 0000000..8c463f8
--- /dev/null
+++ b/help/C/save-session.page
@@ -0,0 +1,30 @@
+<page xmlns="http://projectmallard.org/1.0/";
+      type="topic"
+      id="save-session">
+
+    <info>
+        <link type="guide" xref="index#session"/>
+        <revision version="0.1" date="2013-04-29" status="stub"/>
+        <desc>How to save a Nemiver session</desc>
+    </info>
+
+    <title>Save a debugging session</title>
+
+    <p><app>Nemiver</app> will save debugging sessions automatically when it is
+    closed, so normally you don't have to care about saving your work, however
+    it is possible to save explicitely a session.</p>
+
+    <p>To save a session, choose <guiseq><gui>File</gui><gui>Save Session to 
+    Disk…</gui></guiseq>.</p>
+
+    <section>
+        <title>What is a session</title>
+        <p>A session includes saving information such as which executable is
+        being debugged, what environment variables are set, what command-line
+        options are passed to the executable, which files are open, and which
+        breakpoints are set so that you can get back to where you left off last
+        time as quickly as possible.</p>
+
+    </section>
+
+</page>