-
Notifications
You must be signed in to change notification settings - Fork 166
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
Feature request: support ALE in addition to Syntastic #311
Comments
I don't think ALE is ever going to be able to integrate with OmniSharp-vim. There's a discussion about it at dense-analysis/ale#960 but ALE likes to call standalone linters - it won't integrate with a running server. However, ALE does have an inbuilt LSP implementation, so will be able to bypass OmniSharp-vim and directly deal with the OmniSharp-Roslyn LSP server when that is complete: OmniSharp/omnisharp-roslyn#968. |
so, there is no ideal solution then. |
That's about the state of it. It's not something we can do much about on the OmniSharp side as far as I can tell - ALE has its own way of doing things and doesn't work with long-running processes. If anyone can find a way of doing it it would be brilliant to have ALE support. |
We've got ALE support! I am very happy to have been proved wrong here. We've had some big refactorings, first by @aignas and then by @stevearc. Following that, @stevearc has implemented ALE support with the use of a nice python wrapper script for ALE to execute, which interacts with the OmniSharp server. I've been using it for a couple of days and the async linting is really, really nice. |
I've moved from Syntastic to ALE because it allows for asynchronous syntax checking. Is it possible for OmniSharp to be enhanced to support ALE?
There have been discussions around making Syntastic asynchronous, but it appears to be a big job that may never be completed: vim-syntastic/syntastic#699. ALE leverages Vim 8 jobs to be less intrusive and - for now - is under active development.
The text was updated successfully, but these errors were encountered: