Open jasonyang5 opened 6 years ago
If you do a stack build
and then reopen Sublime Text with stack exec -- subl
(assuming subl
launches Sublime Text) you should be good to go. /cc @mvoidex @bscottm
@moodmosaic: I need a brick to beat against my head. :-)
Whenever I save my files in the sublime text editor I get this error
Uncategorized: Backend error encountered during 'Checking and Linting': module not inspected
and SublimeHaskell doesn't tell me any compile errors in my document. Additionally, I don't get the wrong hsdev-version error when opening sublime text, and I made sure to install the version (0.2.5.1) compatible with sublimeHaskell. And, previous threads mentioned that hsdev works only after you make a project.cabal file that references the file you want to edit. I made sure to do that, and I am still getting the same error.
For reference, I also included what's written in my .cabal file: `name: monad-challenges version: 0.1.0.0 -- synopsis:
-- description:
-- license:
license-file: LICENSE author: Jason -- maintainer: {omitted} -- copyright:
-- category:
build-type: Simple extra-source-files: README.md cabal-version: >=1.10
executable monad-challenges main-is: Main.hs other-modules: Set1.hs other-extensions: MonadComprehensions, RebindableSyntax, Trustworthy, CPP, NoImplicitPrelude, BangPatterns build-depends: base >=4.8 && <4.9 hs-source-dirs: src default-language: Haskell2010`
Thanks! Jason Yang