You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,21 +48,18 @@ If the liquid haskell executable is installed, enable using it to
48
48
process haskell files on save.
49
49
50
50
```
51
-
"languageServerHaskell.hlintOn": true,
51
+
"languageServerHaskell.liquidOn": true,
52
52
```
53
53
54
54
#### HIE Wrapper
55
55
56
56
Furthermore, the extension supports multiple ways of initializing hie,
57
-
depending on your needs. The first one is to use the hie-wrapper that
58
-
follows this extension, and tries to pick the right hie for your GHC
59
-
version. The following,
60
-
61
-
```json
62
-
"languageServerHaskell.useHieWrapper": true,
63
-
```
64
-
65
-
makes VSCode use the `hie-wrapper.sh` file to start hie through. This does assume that you built the hie executable using make build, but will fall back to plain hie. This will take precedence over `hieExecutablePath`.
57
+
depending on your needs. The default one uses the `hie-vscode.[sh|bat]`
58
+
file to start hie through. This will attempt to start via `hie-wrapper`
59
+
if it is on the vscode path, otherwise fall back to `hie`.
60
+
The`hie-wrapper` executable is installed using `make build`,
61
+
together with the other GHC version specific `hie-8.x` executables.
62
+
This will take precedence over `hieExecutablePath`.
0 commit comments