Merge branch 'stable'

borsboom · borsboom · commit 1d44533469f1 · 2017-03-19T09:10:51.000-07:00
diff --git a/doc/GUIDE.md b/doc/GUIDE.md
@@ -1771,6 +1771,22 @@ The `runghc` command is still very useful, especially when you're working on a
 project and want to access the package databases and configurations used by
 that project. See the next section for more information on configuration files.
 
+### Loading scripts in ghci
+
+Sometimes you want to load your script in ghci REPL to play around with your
+program. In those cases, you can use `exec ghci` option in the script to achieve
+it. Here is an example:
+
+```
+#!/usr/bin/env stack
+{- stack
+     --resolver lts-8.2
+     --install-ghc
+     exec ghci
+     --package text
+-}
+```
+
 ## Finding project configs, and the implicit global
 
 Whenever you run something with stack, it needs a `stack.yaml` project file. The
diff --git a/doc/build_command.md b/doc/build_command.md
@@ -86,6 +86,7 @@ of different syntaxes supported for this list:
 
     * `packagename:comptype:compname` is the most explicit. The available
       comptypes are `exe`, `test`, and `bench`.
+        * Side note: When any `exe` component is specified, all of the package's executable components will be built.  This is due to limitations in all currently released versions of Cabal.  See [issue#1046](https://github.com/commercialhaskell/stack/issues/1406)
     * `packagename:compname` allows you to leave off the component type, as
       that will (almost?) always be redundant with the component name. For
       example, `stack build mypackage:mytestsuite`.
