Add a way to make ghc-mod's execution directory customizable #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows us to modify from where ghcmod is executed. Always executing
it from the folder the current file resides in can cause problems with,
for example, Yesod's scaffolding, where some of the splices expect files
to live in certain places relative to the compiler's working directory.
To explain, consider the following: use
yesod init
to create a new default Yesod project, and cd to the new project's directory. Then:Making it possible to set ghc-mod's working directory explicitly allows the user to use Yesod's default scaffolding with ghcmod-vim. There might be another fix, but I can't think of any.