X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fghci.xml;h=35aa7cd279e4cf48400447b93c1425946f8f5c92;hb=f555abffd676544cd13d022bf1eb829e63f7aebe;hp=9fa5d875b0326c6a7f29ebee337aec01452435d3;hpb=c24bd1bbbdc4e20ea5c31b8779a70a5421f44962;p=ghc-hetmet.git
diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml
index 9fa5d87..35aa7cd 100644
--- a/docs/users_guide/ghci.xml
+++ b/docs/users_guide/ghci.xml
@@ -845,10 +845,12 @@ def = toEnum 0
GHCi contains a simple imperative-style debugger in which you can
stop a running computation in order to examine the values of
variables. The debugger is integrated into GHCi, and is turned on by
- default: no flags are required to enable the debugging facilities. There
- is one major restriction: breakpoints and single-stepping are only
- available in interpreted modules; compiled code is
- invisible to the debugger.
+ default: no flags are required to enable the debugging
+ facilities. There is one major restriction: breakpoints and
+ single-stepping are only available in interpreted modules;
+ compiled code is invisible to the debuggerNote that packages
+ only contain compiled code, so debugging a package requires
+ finding its source and loading that directly..
The debugger provides the following:
@@ -883,9 +885,12 @@ def = toEnum 0
There is currently no support for obtaining a “stack
- trace”, but the tracing and history features provide a useful
- second-best, which will often be enough to establish the context of an
- error.
+ trace”, but the tracing and history features provide a
+ useful second-best, which will often be enough to establish the
+ context of an error. For instance, it is possible to break
+ automatically when an exception is thrown, even if it is thrown
+ from within compiled code (see ).
Breakpoints and inspecting variables
@@ -2622,18 +2627,34 @@ Prelude> :set -fno-glasgow-exts
When it starts, unless the -ignore-dot-ghci
- flag is given, GHCi reads and executes commands from
- ./.ghci, followed by
- $HOME/.ghci.
-
- The .ghci in your home directory is
- most useful for turning on favourite options (eg. :set
- +s), and defining useful macros. Placing a
- .ghci file in a directory with a Haskell
- project is a useful way to set certain project-wide options so you
- don't have to type them everytime you start GHCi: eg. if your
- project uses GHC extensions and CPP, and has source files in three
- subdirectories A, B and C, you might put the following lines in
+ flag is given, GHCi reads and executes commands from the following
+ files, in this order, if they exist:
+
+
+
+ ./.ghci
+
+
+ appdata/ghc/ghci.conf,
+ where appdata depends on your system,
+ but is usually something like C:/Documents and Settings/user/Application Data
+
+
+ On Unix: $HOME/.ghc/ghci.conf
+
+
+ $HOME/.ghci
+
+
+
+ The ghci.conf file is most useful for
+ turning on favourite options (eg. :set +s), and
+ defining useful macros. Placing a .ghci file
+ in a directory with a Haskell project is a useful way to set
+ certain project-wide options so you don't have to type them
+ everytime you start GHCi: eg. if your project uses GHC extensions
+ and CPP, and has source files in three subdirectories A, B and C,
+ you might put the following lines in
.ghci:
@@ -2647,7 +2668,7 @@ Prelude> :set -fno-glasgow-exts
until the next :load, though.)
Two command-line options control whether the
- .ghci files are read:
+ startup files files are read:
@@ -2656,8 +2677,8 @@ Prelude> :set -fno-glasgow-exts
- Don't read either ./.ghci or
- $HOME/.ghci when starting up.
+ Don't read either ./.ghci or the
+ other startup files when starting up.
@@ -2666,8 +2687,8 @@ Prelude> :set -fno-glasgow-exts
- Read .ghci and
- $HOME/.ghci. This is normally the
+ Read ./.ghci and the other
+ startup files (see above). This is normally the
default, but the option may
be used to override a previous
option.