Skip to content
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

tags question #23

Closed
timsears opened this issue Apr 6, 2012 · 3 comments
Closed

tags question #23

timsears opened this issue Apr 6, 2012 · 3 comments

Comments

@timsears
Copy link

timsears commented Apr 6, 2012

Have I missed a simple way to get tags for all the modules my project depends on? Currently I manually generate them with hasktags and put them in the project tree. I don't bother with Prelude and other basic packages although sometimes I need to look up definitions from those as well.

@chrisdone
Copy link
Member

Using haskell-process-generate-tags? It just generates based on the current directory only. We could establish an extra variable containing "common" source files to index too?

@timsears
Copy link
Author

timsears commented Apr 6, 2012

The cabal file is a good clue as to what packages the user is likely to need. Can the location of the source files to run through hasktags be inferred easily?

@chrisdone
Copy link
Member

I don't see that the source for the packages is readily available in a typical setting, via Cabal at least.

@timsears timsears closed this as completed Apr 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants