version 0.4

1 files changed, 54 insertions, 10 deletions

diff --git a/doc/mdk_gmixvm.texi b/doc/mdk_gmixvm.texi
index f850384..4cc5399 100644
--- a/doc/mdk_gmixvm.texi
+++ b/doc/mdk_gmixvm.texi
@@ -55,16 +55,31 @@ devices.
 @end itemize
 
 @noindent
+The application can run in two modes: non-split (the above windows are
+placed in a notebook in the main window) or split mode (the windows are
+detached from the main one, and can be hidden individually). You can
+choose the display mode using the menu command @w{Settings->Split
+windows}.
+
+@ifnotinfo
+Here is an screenshot showing how @code{gmixvm} looks like when running
+in split mode:
+
+@image{img/ss_split}
+
+@end ifnotinfo
+
 On the other hand, the main window's lower half presents you a
 @code{mixvm} command prompt and a logging area where results of the
-issued commands are presented. These widgets implement a @code{mixvm}
-console which offers almost the same functionality as its @acronym{CLI}
-counterpart. 
+issued commands are presented (in split mode, these widgets occupy the
+whole main window's space between the menu and status bars). These
+widgets implement a @code{mixvm} console which offers almost the same
+functionality as its @acronym{CLI} counterpart.
 
-When @code{gmixvm} is run, it creates a directory named @file{.gmixvm}
-in your home directory (if it does not already exist). The
-@file{.gmixvm} directory contains the program settings and the device
-files used by your MIX programs (@pxref{Devices}).
+When @code{gmixvm} is run, it creates a directory named @file{.mdk} in
+your home directory (if it does not already exist). The @file{.mdk}
+directory contains the program settings, the device files used by your
+MIX programs (@pxref{Devices}), and a command history file.
 
 The following sections describe the above mentioned components of
 @code{gmixvm}. 
@@ -78,7 +93,7 @@ command text entry and, above it, an echo area. These widgets offer you
 the same functionality as its @acronym{CLI} counterpart, @code{mixvm}
 (@pxref{mixvm}). You can issue almost all @code{mixmv} commands at the
 @code{gmixvm}'s command prompt in order to manipulate the MIX virtual
-machine. Please, refer to @xref{mixvm}, for a description of these
+machine. Please refer to @xref{mixvm}, for a description of these
 commands, and to @xref{Getting started}, for a tutorial on using the MIX
 virtual machine. The command prompt offers command line completion for
 partially typed commands using the @kbd{TAB} key; e.g., if you type
@@ -105,7 +120,10 @@ pmem
 @noindent
 which lists all the available commands starting with @code{p}. In
 addition, the command prompt maintains a history of typed commands,
-which can be recovered using the arrow up and down keys.
+which can be recovered using the arrow up and down keys. As mentioned
+above, a file containing previous sessions' commands is stored in the
+configuration directory @file{~/.mdk}, and reloaded every time you start
+@code{gmixvm}. 
 
 You can change the font used to display the issued commands and the
 messages in the echo area using the @w{Settings->Change font->Command
@@ -138,7 +156,9 @@ displayed in the scrollable list after you click the OK button.
 
 @ifnotinfo
 The next figure shows the enter address dialog.
+
 @image{img/ss_goto}
+
 @end ifnotinfo
 
 
@@ -249,6 +269,16 @@ equivalent to the @code{mixvm}'s @code{run} command (@pxref{Debug
 commands}). 
 @end deffn
 
+@deffn View MIX
+@deffnx View MIXAL
+@deffnx View Devices
+
+These toggles are available when running @code{gmixvm} in split mode,
+and let you turn on/off the visibility of the corresponding
+@code{gmixvm} windows.
+
+@end deffn
+
 @deffn Debug Next
 Executes the next MIX instruction. It is equivalent to the
 @code{mixvm}'s @code{next} command (@pxref{Debug commands}).
@@ -292,6 +322,18 @@ The available formats are decimal (e.g. @w{-1234}) and MIX word
 (e.g. @w{- 00 00 00 19 18}).
 @end deffn
 
+@deffn Settings @w{Devices dir...}
+Opens a dialog that lets you choose where the MIX device files will be
+stored (@file{~/.mdk} is the default location).
+
+@ifnotinfo
+@image{img/ss_devdir}
+@end ifnotinfo
+
+You can also specify the devices directory using the @code{mixvm}
+command @code{devdir} (@pxref{Configuration commands}).
+
+@end deffn
 
 @deffn Settings @w{External programs...}
 This menu command opens a dialog that lets you specify the commands used
@@ -305,7 +347,9 @@ The commands are specified as template strings, where the control
 substring @code{%s} will be substituted by the actual file name. Thus,
 if you want to edit programs using @code{vi} running in an @code{xterm},
 you must enter the command template @code{@w{xterm -e vi %s}} in the
-corresponding dialog entry.
+corresponding dialog entry. These settings can also be changed using the
+@code{mixvm} commands @code{sedit} and @code{sasm} (@pxref{Configuration
+commands}). 
 @end deffn