7 commits

Author	SHA1	Message	Date
w0rp	9fe7b1fe6a	Close #2281 - Separate cwd commands from commands ... Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.	2021-03-01 20:11:10 +00:00
Ian Shipman	2eb68f6d23	#1791 Set the working directory for cabal and stack	2019-04-17 14:26:09 +01:00
w0rp	883978ece9	#2132 - Replace all uses of foo_callback with foo	2019-02-22 18:05:04 +00:00
Robert Estelle	e273f678ff	Add haskell_stack_ghc_options like …_cabal_ghc_… ... Adds new option `g:haskell_stack_ghc_options` which passes options to `stack ghc`. This is implemented similiarly to `g:haskell_cabal_ghc_options`.	2019-01-22 09:46:08 -05:00
Anthony Poon	02c0d5bcb9	Only run stack if a stack.yaml config is found (#1752) ... * Only run stack if a stack.yaml config is found It is necessary to check for a stack.yaml file to distinguish between cabal-only projects or stack projects (which are also cabal projects since stack is built on top of cabal). * Test that stack is called if stack.yaml exists	2018-10-25 15:30:49 +01:00
w0rp	d368f090ae	#1754 Require snake_case names for linters in the codebase	2018-07-24 10:05:44 +01:00
Jake Zimmerman	768f761017	Prefer --fast for stack-build (#754) ... * Vim scripts shouldn't have hyphens Especially not ones that will be autoloaded. You can't have a hyphen in a function name, so autoloading functions based on filename will fail. * Add g:haskell_stack_build_options, default: --fast If we're going to use the --fast option, we may as well go the whole 9 yards and let the user configure the 'stack build' flags. * Create documentation for stack-build options	2017-07-11 13:05:13 +01:00

Renamed from ale_linters/haskell/stack-ghc.vim (Browse further)