-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A command stack docs
that opens the locally installed documentation of packages?
#1396
Comments
On second thought, maybe Without the
|
Sounds like a good idea to me! One tricky thing is what command to use for the browser. I suppose this could be part of How about a
|
Sounds good to me as well. A pull request would be welcome. |
One problem with |
If there isn't already a package on Hackage that provides cross-platform support for opening a browser, one should be created for this issue. |
Node.js has it's There's an |
Was wondering if you all think it'd be viable to have functionality similar to yard, where a command would run a local http server on a given port. This is nice because:
I'm planning on implementing this myself, but I was wondering if anyone here had any comments on this (maybe this is already done/implemented? does it even belong in stack?); opening a new PR might be a bit noisy, as this concept is so closely tied to this one :) |
@mgsloan thanks, i definitely agree, once you put it that way! |
@sjakobi describes how the behavior for this command should be in this PR comment. I'm mentioning this, because I'm closing out the PR due to lack of activity. Also note that that PR is a good starting point. |
For example, from inside the current stack project:
stack docs Cabal
opens~/.stack/snapshots/x86_64-linux/lts-3.14/7.10.2/doc/Cabal-1.22.4.0/index.html
stack --stack-yaml stack-7.8.yaml docs Cabal
opens~/.stack/snapshots/x86_64-linux/lts-2.22/7.8.4/doc/Cabal-1.18.1.5/index.html
Given that stack already installs the documentation for ghc and haddock together with the binaries,
stack docs
could also open these. There needs to be a way to distinguish between the library documentation for haddock and the user guide though.The text was updated successfully, but these errors were encountered: