Skip to content

haskell-compile behaviour #1527

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

Open
vasanthaganeshk opened this issue Jul 27, 2017 · 1 comment
Open

haskell-compile behaviour #1527

vasanthaganeshk opened this issue Jul 27, 2017 · 1 comment

Comments

@vasanthaganeshk
Copy link
Contributor

vasanthaganeshk commented Jul 27, 2017

haskell-compile could work based on something similar to haskell-process-type. Despite the presence of stack.yaml file haskell-compile tries to use something.cabal file. We could implement some kind of priority, we could also take a Makefile into consideration if present.

  • Potential files to work with:
    • haskell-compile.el
@gracjan
Copy link
Contributor

gracjan commented Jul 30, 2017

My half tought out ideas:

  • use projectile to manage project root, which could be either a .cabal or stack.yml file
  • compile based on that

projectile would allow us to store per-project configuration, like how to invoke cabal configure or stack in this specific directory.

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