The ghc-imported-from package

[Tags:bsd3, library, program, test]

Given a Haskell module and symbol, determine the URL to the Haddock documentation for that symbol.

[Skip to Readme]


Change log
Dependencies base (>=4.0 && <5), bytestring, Cabal (>=1.10 && <1.17 || >=1.18), containers, directory, exceptions, filepath, ghc, ghc-imported-from, ghc-mod (==, ghc-paths, ghc-syb-utils, haddock-api, hspec, hspec-discover, monad-journal, mtl, optparse-applicative, parsec, pipes-transduce, process, process-streaming (>=, safe, syb, transformers [details]
License BSD3
Author Carlo Hamalainen
Category Development
Home page
Uploaded Wed Jun 1 09:51:54 UTC 2016 by CarloHamalainen
Distributions NixOS:
Downloads 2726 total (11 in the last 30 days)
0 []
Status Docs not available [build log]
All reported builds failed as of 2016-11-24 [all 3 reports]


  • Language
    • Haskell
      • Language.Haskell.GhcImportedFrom


Maintainer's Corner

For package maintainers and hackage trustees

Readme for ghc-imported-from

Readme for ghc-imported-from-


For a given Haskell source file, determine the path to the Haddock documentation for a symbol at a particular line/col location.

Example: on the file src/Main.hs,

ghc-imported-from src/Main.hs Main strOption 18 17


SUCCESS: file:///home/carlo/.stack/snapshots/x86_64-linux/lts-5.8/7.10.3/doc/optparse-applicative-

since the usage of strOption at line 18, column 17, is from the Options.Applicative.Builder module.

Difficulties arise in resolving names because some symbols are exported from a certain package but defined in another, for example String is defined in GHC.Base but is exported from the standard prelude, the module Prelude. There are other cases to deal with including qualified imports, selective imports, imports with hidden components, etc.

Using with Stack

Stack makes everything easier.

Build ghc-imported-from:

git clone
cd ghc-imported-from
stack build

then add


or similar to your $PATH.

Then in a project that you are working on:

cd my-project
stack build
stack haddock # Must do this!
ghc-imported-from some/file/Blah.hs Blah f 100 3


Run the tests using Stack:

stack test


For Vim users, follow the instructions at to install the Vim plugin.


For Emacs users, David Christiansen has written ghc-imported-from-el.


See the tests subdirectory for some examples. Or load your favourite Haskell project and hit F4.

Or watch the screencast (be sure to set 720p HD and then fullscreen):


ghc-imported-from uses both GHC and ghc-pkg, which accept arguments in differing formats. For example GHC takes -package-db while ghc-pkg takes --package-db=. For more details:


To see the GHC options that have been automatically detected, change into your project's directory and run:

$ cd ~/ghc-imported-from
$ cabal repl --with-ghc=fake-ghc-for-ghc-imported-from
Preprocessing library ghc-imported-from-
--interactive -fbuilding-cabal-package -O0 -outputdir dist/build -odir dist/build -hidir dist/build -stubdir dist/build -i -idist/build -i. -idist/build/autogen -Idist/build/autogen -Idist/build -optP-include -optPdist/build/autogen/cabal_macros.h -package-name ghc-imported-from- -hide-all-packages -no-user-package-db -package-db /home/user/ghc-imported-from/.cabal-sandbox/x86_64-linux-ghc-7.6.3-packages.conf.d -package-db dist/package.conf.inplace -package-id Cabal-1.16.0-c6e09e008cd04cf255c1ce0c59aba905 -package-id base- -package-id containers- -package-id directory- -package-id filepath- -package-id ghc-7.6.3-18957ddbb817289f604552aa2da2e879 -package-id ghc-mod-4.1.0-a87501f2667239b3f0bef3e0f3753496 -package-id ghc-paths- -package-id ghc-syb-utils- -package-id mtl- -package-id process- -package-id safe-0.3.4-ba52ca348aecad429ba90450e3aba4c4 -package-id syb-0.4.1-9469ffdd9c6a7ebbf035421c915a08ee -package-id transformers- -XHaskell2010 Language.Haskell.GhcImportedFrom Language.Haskell.GhcImportedFrom.UtilsFromGhcMod Language.Haskell.GhcImportedFrom.Types -Wall


As far as I know the only alternative is the fpco/hoogle-doc function in Or try Ctrl-i in the web version of FP Complete.