Merge remote-tracking branch 'origin/stable'

Author: borsboom

doc/GUIDE.md

@@ -1157,6 +1157,10 @@ Flags worth mentioning:
   variable from being set. Some tools — notably cabal-install — do not behave
   well with that variable set.
 
+You may also find it convenient to use `stack exec` to launch a subshell (substitute `bash` with your preferred shell) where your compiled executable is available at the front of your `PATH`:
+
+    stack exec bash
+
 ## ghci (the repl)
 
 GHCi is the interactive GHC environment, a.k.a. the REPL. You *could* access it

doc/build_command.md

@@ -96,8 +96,6 @@ of different syntaxes supported for this list:
       the local packages." This will result in an error if multiple packages
       have a component with the same name. To continue the above example,
       `stack build :mytestsuite`.
-        * Side note: the commonly requested `run` command is not available
-          because it's a simple combination of `stack build :exename && stack exec exename`
 
 * *directory*, e.g. `stack build foo/bar`, will find all local packages that
   exist in the given directory hierarchy and then follow the same procedure as

doc/yaml_configuration.md

@@ -41,7 +41,7 @@ user's local packages, these dependencies aren't built by default. They only get
 built when needed.
 
 Shadowing semantics, described
-[here](http://docs.haskellstack.org/en/stable/architecture/#shadowing), are
+[here](https://docs.haskellstack.org/en/v1.5.1/architecture/#shadowing), are
 applied to your configuration. So, if you add a package to your `packages` list,
 it will be used even if you're using a snapshot that specifies a particular
 version. Similarly, `extra-deps` will shadow the version specified in the