Split command line generation for cabal build and stack build

[fatlazycat]

Hi, probably my own lack of knowledge but I use haskell-session-change-target to set the target to be the test of my cabal file within a stack project.

When I start the repl it fails to find modules defined within the test target.

What obvious stupid thing am I doing wrong ? :)

Thanks

[geraldus]

@fatlazycat hi! How do you start your REPL by the way?

[geraldus]

haskell-session-change-target also fails for me when I select executable. What is the purpose of target selection? Usually I'm either reloading file in REPL C-c C-l or running build command C-c C-c.

[fatlazycat]

In a test Haskell file, i do haskell-session-change-target then start the REPL (I'm using spacemacs) SPC m s b to load the current file into the REPL which i believe is function haskell-process-load-file.

[fatlazycat]

Is the there a difference given I would start a stack repl with

stack repl 'project name':test:'test target'

?

[fatlazycat]

Ah, can get it to work if I type that pattern when i do haskell-session-change-target so can work around it.

Guess the targets are just incorrect as it's just showing the cabal versions ?

[geraldus]

@gracjan can you help with this? I have no much experience personally. I guess target selecting makes some sense when running C-c C-c haskell-process-cabal-build. I'm not sure.

[gracjan]

I tried to understand what you are talking about here but no avail. I'm lost. What is the problem again?

[fatlazycat]

Sorry, when showing the targets for haskell-session-change-target for a stack based project I see the cabal entries for executables & test suites.

But when attempting to use any, such as the test target, it does not start CHCI correctly.

I assume it's running the command stack ghci test-suite

But as far as I understand for a stack project you want to invoke it as

stack ghci project-name:test:test-suite

[gracjan]

Ah, now it is clear as sun.

You are right that command line invocation is the same for cabal and stack projects, as I see it started to diverge. We have to split this functionality into two: cabal and stack.

Should not be that hard. @fatlazycat, are you able to look at this?

[fatlazycat]

Sure will try and take a look.

[gracjan]

Great!

[fatlazycat]

@gracjan from http://docs.haskellstack.org/en/stable/build_command/#target-syntax the targets have changed for build etc as well as ghci . Can you see any reason why I wouldn't change the targets it gets from the cabal file for haskell-cabal-enum-targets ?

[gracjan]

We still support plain cabal so we cannot drop old target syntax.