Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integrate lsp-ui with flychecker (develop branch) #10709

Closed
dagadbm opened this issue May 20, 2018 · 3 comments
Closed

integrate lsp-ui with flychecker (develop branch) #10709

dagadbm opened this issue May 20, 2018 · 3 comments
Labels
stale marked as a stale issue/pr (usually by a bot)

Comments

@dagadbm
Copy link

dagadbm commented May 20, 2018

Apparently lsp-ui is already included in the javascript/react layer but flychecker isn't using it. I get this message when i do SPC e v:

The following syntax checkers are not registered:

  • lsp-ui

Try adding these syntax checkers to `flycheck-checkers'. Flycheck Mode is
enabled. Use SPC u C-c ! x to enable disabled checkers.

Shouldn't this be done automatically by the layer or by flychecker?

How to fix this? (Should this be addresed by the layer)

@mspinelli
Copy link

mspinelli commented Jul 31, 2018

@dagadbm Adding the last line below seemed to work for me in dotspacemacs/user-config ()

  (require 'lsp-mode)
  (require 'lsp-ui)
  (add-hook 'lsp-mode-hook 'lsp-ui-mode)
  (add-hook 'lsp-ui-mode-hook 'flycheck-mode)

At least fixing that error. But sadly linting still isn't working. See AdamNiederer/vue-mode#84

@msuess
Copy link
Contributor

msuess commented Aug 14, 2018

<SPC e v> is looking good on a fresh pull, with lsp-ui being enabled and executable and config file being reported as found.

Flycheck does not show any errors however.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

3 participants