generate tags files and install them with source files #200

bos opened this Issue May 24, 2012 · 2 comments


None yet

2 participants

bos commented May 24, 2012

(Imported from Trac #207, reported by guest on 2008-01-14)


I personally depend on tags because the source code only tells what is really going on.
So it would be incredible useful to not only get information using ghci after loading libs but also beeing able to jump to all functions you might be using anywhere (The only solution providing this in all cases is uning tags, right? Because cpp defines can introduce new functions.. To be able to jump to the code source must be installed along with libs (the way you can optionally install haddock docs)

Use case:

setup configure --with-tags --install-source (or something like that)
setup build && setup install

do this for each dependency given in the .cabal file
(VIM:) let tags+=system('ghc-pkg --query-tagfile-location haskell98-')


- Which tool to generate tag files?
  • ghc(i) when targeting ghc
  • the hasktags program shipping with ghc
  • some others?
\* Tagfile path type relative or absolute?
  • absolute: After moving/ installing the sources the tagfile must be patched
  • relative: Do editors take the right base directory to find source files?
\* When to invoke the tagfile generating program?
  • Perfect case would be after all preprocessing has been done (Thus the tagging program should understand line number changing comments!)
\* Template Haskell? ( This is really tricky I think ) - Hmm sorted tagfiles would be useful as well :)

alternatives ?

If you do not think this is useful (mandatory?)

how do you lookup code? (Yes I know hoogle :) perhaps using Eclipse or Visual Studio?

I'd like to start implementing this somehow the next weeks.
So don't hesitate and start discussing

Marc Weber

bos commented May 24, 2012

(Imported comment by guest on 2008-01-14)

Most of the discussion will take place on haskell-cafe (mailinglist).

tibbe commented May 5, 2014

Closing as there's been no activity in years.

We're cleaning up the bug tracker to make it useful again and are thus closing bugs that haven't seen any activity in a long time. Please re-open (or file a new bug) if the problem reappears.

@tibbe tibbe closed this May 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment