Enable hlint on multi projects by default #69
Comments
|
Strange, on my PC it's always on by default. But if you want to run that in every new buffer you could probably just do |
|
Thank you very much. After trying different files I figured out the issue seems to persists with multi projects only, i.e. projects using a hie.yaml. Other projects work as expected. |
marcellussiegburg
changed the title
michaelpj
added a commit
to michaelpj/lsp-haskell
that referenced
this issue
Sep 18, 2020
This does two things: - Create `defcustom` variables for settings, matching the vscode extension for all the language server settings. - Use `lsp-mode`'s support for custom settings to handle sending them to the server. This lets users persistently configure their server settings using normal Emacs setting customization. This will probably break people, so should maybe be a major version bump. Fixes emacs-lsp#69, emacs-lsp#75, emacs-lsp#78; supersedes the (excellent) emacs-lsp#74 and emacs-lsp#76. Notes: - I have not copied the settings from the vscode extension regarding starting the server. We don't try and get prebuilt binaries, so I thought it was simplest to stick to command-and-arguments. - I renamed the process option for consistency with other servers and to avoid references to `hie`. This PR will already break basically everyone, so I thought I might as well do that too. - The current customization functions re-send a `didChangeConfiguration` notification when called. `lsp-mode` does *not* currently do this when you change variables, which is annoying. My inclination is to let them fix it in the name of simplicity, but if anyone really hates not being able to change the formatter without restarting the server I can try and hack something together.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way of enabling hlint by default? I could not figure out how.
It seems there is no way of setting this within my
.emacsfile.I know that I can call
lsp-haskell-set-hlint-onon every file or setting file-local-variables (maybe even dir-local-variables?, though being unable to setting it up); but I want hlint being enabled always anyway.The text was updated successfully, but these errors were encountered: