Using with a stack project (e.g. hakyll)

[jonboiser]

I installed hdevtools with stack install and tested linter-hdevtools with simple standalone scripts.

I have a hakyll project and have gotten the hdevtools CLI to work e.g.

hdevtools check site.hs

But I don't get any linting information when I am editing site.hs inside of Atom.

I uncommented the console.log at https://github.com/ranjitjhala/linter-hdevtools/blob/master/lib/init.coffee#L31

And here is what I see:

begin:Run from outside a project, using implicit global project config

Cabal error: At least the following dependencies are missing:
    hakyll ==4.8.*
:end

As far as the package is concerned, this is not actionable information, since it has no file name, line number etc.

I can reproduce the same behavior with the CLI by, say going a directory up and doing

hdevtools check ./hakyll-blog/site.hs

I'm just wondering if there's something wrong with my stack setup, the linter library, or anything else?

BTW, I'm a UCSD alumnus and have been wanting to look into Liquid Haskell soon!

[ranjitjhala]

1. Do you have a stack.yaml in the root of your project? Ie hakyll-blog/stack.yaml?
2. If not can you create one, do a killall hdevtools and restart atom?

[ranjitjhala]

Also how are you opening atom?

[ranjitjhala]

Also since you installed hdevtools with stack did you check the use stack
option (for the plugin)?

On Sunday, June 12, 2016, Jonathan Boiser notifications@github.com wrote:

I installed hdevtools with stack install and tested linter-hdevtools with
simple standalone scripts.

I have a hakyll project and have gotten the hdevtools CLI to work e.g.

hdevtools check site.hs

But I don't get any linting information when I am editing site.hs inside
of Atom.

I uncommented the console.log at
https://github.com/ranjitjhala/linter-hdevtools/blob/master/lib/init.coffee#L31

And here is what I see:

begin:Run from outside a project, using implicit global project config

Cabal error: At least the following dependencies are missing:
hakyll ==4.8.*
:end

As far as the package is concerned, this is not actionable information,
since it has no file name, line number etc.

I can reproduce the same behavior with the CLI by, say going a directory
up and doing

hdevtools check ./hakyll-blog/site.hs

I'm just wondering if there's something wrong with my stack setup, the
linter library, or anything else?

BTW, I'm a UCSD alumnus and have been wanting to look into Liquid Haskell
soon!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#9, or mute the
thread
https://github.com/notifications/unsubscribe/ABkuOG-i94zi2ZnND-uzGvZk2_oX9PZUks5qLKg6gaJpZM4Iz7R-
.

[jonboiser]

1. I do have a stack.yaml: https://github.com/jonboiser/hakyll-blog/blob/master/stack.yaml
2. I open atom using atom inside of iTerm
3. The 'use stack' option is set. When I run something like stack exec hdevtools -- check site.hs inside my project directory, it works fine.

[ranjitjhala]

Puzzling.

Can you uncomment the line

console.warn(command, args)

And tell me what gets printed out in the log?

On Sunday, June 12, 2016, Jonathan Boiser notifications@github.com wrote:

1. I do have a stack.yaml:
   https://github.com/jonboiser/hakyll-blog/blob/master/stack.yaml
2. I open atom using atom inside of iTerm
3. The 'use stack' option is set. When I run something like stack exec
   hdevtools -- check site.hs inside my project directory, it works fine.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABkuOD86Pq2WZPiwqiICzZEIFk7W5tCWks5qLPcngaJpZM4Iz7R-
.

[jonboiser]

stack ["exec", "--no-ghc-package-path", "hdevtools", "--", "check", "-s", "~/.hdevtools-socket-atom-lint", "-g", "-Wall", "-g", "-Werror", "~/Projects/hakyll-blog/site.hs"] (I aliased the home directory to ~).

Again, tried that stack command inside of the project directory and it was fine.

[ranjitjhala]

Hmm. Not sure if this helps, but I can't get hdevtools to work from the CLI (on your repo), its producing the same odd error (but now in the CLI).

rjhala@borscht ~/t/hakyll-blog (master) [1]> stack exec hdevtools -- check site.hs
Cabal error: Use of GHC's environment variable GHC_PACKAGE_PATH is incompatible with Cabal. Use the flag --package-db to specify a package database (it can be used multiple times).

rjhala@borscht ~/t/hakyll-blog (master)> stack exec --no-ghc-package-path hdevtools -- check -s /Users/rjhala/.hdevtools-socket-atom-lint site.hs  
Cabal error: At least the following dependencies are missing:
    hakyll ==4.8.*

rjhala@borscht ~/t/hakyll-blog (master) [1]> stack exec --no-ghc-package-path hdevtools -- check site.hs  
Cabal error: At least the following dependencies are missing:
    hakyll ==4.8.*

rjhala@borscht ~/t/hakyll-blog (master) [1]> stack exec --no-ghc-package-path hdevtools -- check site.hs  
Cabal error: At least the following dependencies are missing:
    hakyll ==4.8.*

Can you tell me what you get when you do:

$ stack exec -- hdevtools --version

Also, can you double check that hdevtools is working from the CLI after first killing it?
i.e.

$ killall hdevtools
$ stack exec hdevtools -- check site.hs

(I wonder if this because the version GHC that hdevtools is using is different than the on used by lts-6.1?)

[jonboiser]

➜ stack exec -- hdevtools --version
hdevtools: version 0.1.3.1 (ghc-7.10.3-x86_64-darwin, cabal-1.22.8.0)

After killall, I also get the error message

killall hdevtools
stack exec hdevtools -- check site.hs
Cabal error: Use of GHC's environment variable GHC_PACKAGE_PATH is incompatible with Cabal. Use the flag --package-db to specify a package database (it can be used multiple times).

This all seems random to me. I've tried deleting my ~/.stack folder and to start from scratch and get some reproducible results.