Skip to content
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.

Support ALE #82

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Support ALE #82

wants to merge 1 commit into from

Conversation

tunz
Copy link

@tunz tunz commented Jun 9, 2017

ALE is an asynchronous syntax checker (similar with syntastic). it seems that syntastic does not support asynchronous for a while (vim-syntastic/syntastic#699 (comment)), and ALE is growing quickly. so, I think it's valuable to support ALE, and I'm actually using it.

Is it considerable?

@kjnilsson
Copy link
Contributor

kjnilsson commented Jun 9, 2017 via email

@kjnilsson
Copy link
Contributor

Really sorry I haven't been able to spend more time on this. I think ALE support looks really promising. What is the story for using ALE and syntastic at the same time? Should users disable fsharp support for syntastic when using ALE and vice versa?

@tunz
Copy link
Author

tunz commented Oct 3, 2017

I'm currently using only ALE. I've never tried to use both of ALE and syntastic at the same time. I guess users should disable one of ALE or syntastic.

@palutz
Copy link

palutz commented Jan 19, 2018

It could be really interesting. Any news on this?

@kjnilsson
Copy link
Contributor

no news @palutz - I could do with a hand testing this with both ALE and syntastic installed.

@palutz
Copy link

palutz commented Jan 23, 2018

@kjnilsson, I actually tried but got some conflicts with both installed.
I was also wondering if it's possible to have autocompletion/intellisense with vim-fsharp cause I'm not able to set it up (most of the time it's fine, but when trying some new libs it could be helpful)

@wsdjeg
Copy link

wsdjeg commented Aug 23, 2018

@tunz This file should be included in ale repo, not all vim-fsharp users use ale.

@tunz
Copy link
Author

tunz commented Aug 23, 2018

@wsdjeg then why do we have syntastic support in this repo? not all vim-fsharp users use syntastic.
this repository implemented interactions with fsautocomplete to find errors of codes, and this script is just wrapping the implementation.

@wsdjeg
Copy link

wsdjeg commented Aug 23, 2018

ok, it is a good reason.

@roper79
Copy link

roper79 commented May 26, 2019

Hi, are there some advancements, please?

@tunz
Copy link
Author

tunz commented May 27, 2019

@kjnilsson FYI, I don't have any problem even when both of ale and syntastic are installed at the same time. Each of them works well.

@PhilT
Copy link

PhilT commented Jul 12, 2019

Any chance we can get this merged? Would be pretty useful.

@wsdjeg
Copy link

wsdjeg commented Jul 12, 2019

there are too many lint plugins. should this repo includ all of tham? why only ale?

still think this should be included in ale repo. as maybe ale's api may changed in future.

@PhilT
Copy link

PhilT commented Jul 12, 2019

Fair point but syntastic is no longer a sensible default. Perhaps Ale should be?

@wsdjeg
Copy link

wsdjeg commented Jul 12, 2019 via email

@PhilT
Copy link

PhilT commented Jul 12, 2019

You're right. Maybe we are going about this wrong. ALE is all about supporting as many languages as possible. Perhaps we should add support in ALE instead.

@baronfel
Copy link

As an alternative, I see that ALE supports the Language Server Protocol. I would look at using the new LSP mode for FSAutoComplete and integrating that into ALE, as has been done for VSCode via Ionide and FSharp-Language-Server, and emacs via lsp-mode.

@kjnilsson
Copy link
Contributor

kjnilsson commented Jul 12, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants