@@ -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
@@ -1227,7 +1227,7 @@ to build.
12271227
12281228We're not going to cover the full generality of these arguments here; instead,
12291229there's [documentation covering the full build command
1230- syntax](build_command.html ).
1230+ syntax](build_command.md ).
12311231Here, we'll just point out a few different types of arguments :
12321232
12331233* You can specify a *package name*, e.g. `stack build vector`.
@@ -1364,7 +1364,7 @@ In addition to local directories, you can also refer to packages available in a
13641364Git repository or in a tarball over HTTP/HTTPS. This can be useful for using a
13651365modified version of a dependency that hasn't yet been released upstream. This is
13661366a slightly more advanced usage that we won't go into detail with here, but it's
1367- covered in the [stack.yaml documentation](yaml_configuration.html #packages).
1367+ covered in the [stack.yaml documentation](yaml_configuration.md #packages).
13681368
13691369# # Flags and GHC options
13701370
@@ -1452,7 +1452,7 @@ confusion.
14521452Final point : if you have GHC options that you'll be regularly passing to your
14531453packages, you can add them to your stack.yaml file (starting with
14541454stack-0.1.4.0). See [the documentation section on
1455- ghc-options](yaml_configuration.html #ghc-options)
1455+ ghc-options](yaml_configuration.md #ghc-options)
14561456for more information.
14571457
14581458# # path
@@ -1745,7 +1745,7 @@ There are lots of resources available for learning more about stack:
17451745* `--verbose` (or `-v`) — much more info about internal operations (useful for bug reports)
17461746* The [home page](http://haskellstack.org)
17471747* The [stack mailing list](https://groups.google.com/d/forum/haskell-stack)
1748- * The [the FAQ](faq.html )
1748+ * The [the FAQ](faq.md )
17491749* The [stack wiki](https://github.com/commercialhaskell/stack/wiki)
17501750* The [haskell-stack tag on Stack Overflow](http://stackoverflow.com/questions/tagged/haskell-stack)
17511751* [Another getting started with stack tutorial](http://seanhess.github.io/2015/08/04/practical-haskell-getting-started.html)
@@ -1802,13 +1802,13 @@ getting type information in Emacs. For more information, see
18021802
18031803If you'd like to get some insight into the dependency tree of your packages, you
18041804can use the `stack dot` command and Graphviz. More information is
1805- [available in the Dependency visualization documentation](dependency_visualization.html ).
1805+ [available in the Dependency visualization documentation](dependency_visualization.md ).
18061806
18071807### Travis with caching
18081808
18091809Many people use Travis CI to test out a project for every Git push. We have [a
18101810document devoted to
1811- Travis](travis_ci.html ). However, for
1811+ Travis](travis_ci.md ). However, for
18121812most people, the following example will be sufficient to get started:
18131813
18141814```yaml
@@ -1998,7 +1998,7 @@ code inside a Docker image, which means:
19981998 a large initial download, but much faster builds
19991999
20002000For more information, see
2001- [ the Docker-integration documentation] ( docker_integration.html ) .
2001+ [ the Docker-integration documentation] ( docker_integration.md ) .
20022002
20032003stack can also generate Docker images for you containing your built executables.
20042004This feature is great for automating deployments from CI. This feature is not
@@ -2062,7 +2062,7 @@ in the common case or even to learn how to use the Nix tools (they're
20622062called under the hood).
20632063
20642064For more information, see
2065- [the Nix-integration documentation](nix_integration.html ).
2065+ [the Nix-integration documentation](nix_integration.md ).
20662066
20672067# # Power user commands
20682068
0 commit comments