-
Notifications
You must be signed in to change notification settings - Fork 167
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
ALE Not working with "No Configuration" #863
Comments
Don't worry about that "Available Linters" line in Have a look at the log to see if there are any issues with the server: |
Seems like failures around
and
|
Yeah the server isn't running properly. I can't tell more from the partial log |
|
Apologies for giving the wrong log. I opened up the git bash one and ran the :OmniSharpOpenLog command. I had attempted to do it there first, but then ran across an older issue where you recommend wsl. it is wsl 2. There is only one Log Error on the WSL 2 Ubuntu instance. I haven't even built the project. Didn't know this lsp required a successful build of a project first. I will go try that after providing this configuration. call plug#begin()
Plug 'dense-analysis/ale'
Plug 'OmniSharp/omnisharp-vim'
call plug#end()
let g:OmniSharp_translate_cygwin_wsl = 1
let g:ale_linters_explicit = 1
let g:ale_completion_enabled = 1
set omnifunc=ale#completion#OmniFunc
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_hover_to_preview = 1
let g:ale_fix_on_save = 1
let g:ale_linters = { 'javascript': ['eslint', 'tsserver'], 'typescript': ['eslint', 'tsserver'],
\ 'rust': ['analyzer'], 'zig': ['zls'], 'python': ['pyright'], 'cs' : ['OmniSharp']
\ } |
No it doesn't need a built project, but it's relevant whether the file paths are Windows style or unix style. Did you create the project on the WSL side, e.g. with If you are running/building/developing in WSL then you shouldn't use Instead, you should use |
After a successful build with no Errors, and no Warnings. I uninstalled omnisharp-vim and set to use net6. I reinstalled omnisharp-vim and ran OmniSharpInstall. The path shown in output mentioned net 6. and the installation is there.
When attempting to open the same cs file I now get
and if I run it shows |
Can you share the log please? |
If you run |
That error is not in the logs, just in the command window when opening a cs file.
Is it recommended to use wsl2 tunnel to windows and build on windows, or build within wsl2? |
dotnet --info output
|
When I run
Where does Omnisharp look for an installed sdk? My path in
|
I don't recommend it. The only reason you'd do that is if you are using something on the Windows side, like Visual Studio, and need to switch between VS and vim. If you're exclusively developing in WSL, that makes things much simpler. |
This is server configuration stuff, it's outside my area. But I think it's just using It might be worth taking vim out of the picture for a bit and try just running the server manually. cd /path/to/project/or/sln
~/.cache/omnisharp-vim/omnisharp-roslyn/OmniSharp -l debug That will produce hopefully a lot of output that you can use to deduce what it's missing, and where it's looking. |
I'm really not sure if this can have an effect but my understanding is that |
I added and I now have seemingly all lsp capabilities :) After a while of having this going since I need to make progress now, I will make the adjustment to work across windows/wsl boundary at a later time. |
I have ALE installed, and omnisharp-vim installed with Plug.
I am on WSL ubuntu. I can see the ale_linters directory in omnisharp vim in my local plugged folder. Everything looks good there.
It appears the omnisharp option is not available. I have ran
:OmnisharpInstall
And it appears to be running well.
Output of :OmniSharpStatus
pid: 10207
Loaded server for /home/chris/path/SolutionName.sln in 7.8s
Output of :ALEInfo
Available Linters: ['csc', 'cspell', 'mcs', 'mcsc']
edit
Forgot to mention that I have set the ale_linters as well
The text was updated successfully, but these errors were encountered: