From: Ian Lynagh <igloo@earth.li>
Date: Sun, 3 Sep 2006 22:21:15 +0000 (+0000)
Subject: Ambiguities are now allowed in ghci command names
X-Git-Tag: Before_FC_branch_merge~82
X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=commitdiff_plain;h=8eb677bc6758080886aa8b21340cc3470b249b75

Ambiguities are now allowed in ghci command names
---

diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml
index e79fb46..26efdee 100644
--- a/docs/users_guide/ghci.xml
+++ b/docs/users_guide/ghci.xml
@@ -873,10 +873,8 @@ $ ghci -lm
     <para>GHCi commands all begin with
     &lsquo;<literal>:</literal>&rsquo; and consist of a single command
     name followed by zero or more parameters.  The command name may be
-    abbreviated, as long as the abbreviation is not ambiguous.  All of
-    the builtin commands, with the exception of
-    <literal>:unset</literal> and <literal>:undef</literal>, may be
-    abbreviated to a single letter.</para>
+    abbreviated, with ambiguities being resolved in favour of the more
+    commonly used commands.</para>
 
     <variablelist>
       <varlistentry>