Improve troubleshooting and installation docs a bit #3004
Conversation
|
If optparse-applicative was able to generate manpages, we could just upload a ghcup manpage: pcapriotti/optparse-applicative#176 |
| and `stack install --stack-yaml stack-<GHCVER>.yaml`, is not recommended for most people. | ||
| Said command builds the `haskell-language-server` binary and installs it in the default Cabal binaries folder, | ||
| Said command builds the `haskell-language-server` binary and installs it in the default `cabal` binaries folder, | ||
| but the binary will only work with projects that use the same GHC version that built it. |
There was a problem hiding this comment.
Can we somehow highlight this line a little?
I personally had missed this while skimming through the docs and realized it later on. I think adding it as a note maybe can highlight the point.
Edit: This as in:
the binary will only work with projects that use the same GHC version that built it.
There was a problem hiding this comment.
I think this section shouldn't be emphasized anyway and there is a section about this on the troubleshooting page already (which hopefully people actually read...).
There was a problem hiding this comment.
Generally there is a lot of stuff in the installation doc, and I wonder if it could be organized better 🤔
|
Can I get an approve? :) |
ghcup compilecabal updatetoghcup compileinstructions in troubleshooting.md #2799 and Troubleshooting: Add solution from #1882 #2795