@@ -48,7 +48,7 @@ all commands work cross-platform, unless explicitly stated otherwise.
4848## Downloading and Installation
4949
5050The [ documentation dedicated to downloading
51- stack] ( install_and_upgrade.html ) has the most
51+ stack] ( install_and_upgrade.md ) has the most
5252up-to-date information for a variety of operating systems, including multiple
5353GNU/Linux flavors. Instead of repeating that content here, please go check out
5454that page and come back here when you can successfully run ` stack --version ` .
@@ -619,7 +619,7 @@ At the time of writing:
619619* Experimental custom snapshot support
620620
621621The most up-to-date information can always be found in the
622- [stack.yaml documentation](yaml_configuration.html #resolver).
622+ [stack.yaml documentation](yaml_configuration.md #resolver).
623623
624624# # Existing projects
625625
@@ -725,7 +725,7 @@ Please choose one of the following commands to get started.
725725 stack init --resolver lts-2.22
726726
727727You'll then need to add some extra-deps. See the
728- [stack.yaml documentation](yaml_configuration.html #extra-deps).
728+ [stack.yaml documentation](yaml_configuration.md #extra-deps).
729729
730730You can also try falling back to a dependency solver with:
731731
@@ -1028,7 +1028,7 @@ to build.
10281028
10291029We're not going to cover the full generality of these arguments here; instead,
10301030there's [documentation covering the full build command
1031- syntax](build_command.html ).
1031+ syntax](build_command.md ).
10321032Here, we'll just point out a few different types of arguments :
10331033
10341034* You can specify a *package name*, e.g. `stack build vector`.
@@ -1165,7 +1165,7 @@ In addition to local directories, you can also refer to packages available in a
11651165Git repository or in a tarball over HTTP/HTTPS. This can be useful for using a
11661166modified version of a dependency that hasn't yet been released upstream. This is
11671167a slightly more advanced usage that we won't go into detail with here, but it's
1168- covered in the [stack.yaml documentation](yaml_configuration.html #packages).
1168+ covered in the [stack.yaml documentation](yaml_configuration.md #packages).
11691169
11701170# # Flags and GHC options
11711171
@@ -1253,7 +1253,7 @@ confusion.
12531253Final point : if you have GHC options that you'll be regularly passing to your
12541254packages, you can add them to your stack.yaml file (starting with
12551255stack-0.1.4.0). See [the documentation section on
1256- ghc-options](yaml_configuration.html #ghc-options)
1256+ ghc-options](yaml_configuration.md #ghc-options)
12571257for more information.
12581258
12591259# # path
@@ -1546,7 +1546,7 @@ There are lots of resources available for learning more about stack:
15461546* `--verbose` (or `-v`) — much more info about internal operations (useful for bug reports)
15471547* The [home page](http://haskellstack.org)
15481548* The [stack mailing list](https://groups.google.com/d/forum/haskell-stack)
1549- * The [the FAQ](faq.html )
1549+ * The [the FAQ](faq.md )
15501550* The [stack wiki](https://github.com/commercialhaskell/stack/wiki)
15511551* The [haskell-stack tag on Stack Overflow](http://stackoverflow.com/questions/tagged/haskell-stack)
15521552* [Another getting started with stack tutorial](http://seanhess.github.io/2015/08/04/practical-haskell-getting-started.html)
@@ -1603,13 +1603,13 @@ getting type information in Emacs. For more information, see
16031603
16041604If you'd like to get some insight into the dependency tree of your packages, you
16051605can use the `stack dot` command and Graphviz. More information is
1606- [available in the Dependency visualization documentation](dependency_visualization.html ).
1606+ [available in the Dependency visualization documentation](dependency_visualization.md ).
16071607
16081608### Travis with caching
16091609
16101610Many people use Travis CI to test out a project for every Git push. We have [a
16111611document devoted to
1612- Travis](travis_ci.html ). However, for
1612+ Travis](travis_ci.md ). However, for
16131613most people, the following example will be sufficient to get started:
16141614
16151615```yaml
@@ -1689,7 +1689,7 @@ code inside a Docker image, which means:
16891689 a large initial download, but much faster builds
16901690
16911691For more information, see
1692- [ the Docker-integration documentation] ( docker_integration.html ) .
1692+ [ the Docker-integration documentation] ( docker_integration.md ) .
16931693
16941694stack can also generate Docker images for you containing your built executables.
16951695This feature is great for automating deployments from CI. This feature is not
@@ -1749,7 +1749,7 @@ in the common case or even to learn how to use the Nix tools (they're
17491749called under the hood).
17501750
17511751For more information, see
1752- [the Nix-integration documentation](nix_integration.html ).
1752+ [the Nix-integration documentation](nix_integration.md ).
17531753
17541754# # Power user commands
17551755
0 commit comments