WSL2+ale-lint-other-machines (Windows) #4432
Unanswered
gastmaier
asked this question in
Q&A - Ask for help with problems
Replies: 1 comment 1 reply
-
I think I made progress replacing the PowerShell script by this gorgeous clangd.bat:
which indicates that ALE will use cmd.exe even if the shell is set to PowerShell.
instead of Note: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to use vim ALE in the same way VSCode server works in WSL2, by running the linters in the container and the IDE in the Host.
At Linting On Other Machines - doc/ale.txt I thought I got what I wanted,
however I can't figure out how to change the "docker in bash" example by a "wsl2 in powershell".
What I tried (targeting only one container):
At .vimrc:
At clangd.ps1:
Sequence of commands after launching vim.exe:
ALEInfoClipboard output:
The
g:ale_cpp_clangd_executable
andg:ale_linters
enabled just fine, but the powershell script does not seem to be being called...With
!C:\Users\me\work\share\linters\clangd.ps1 ls
I get:just as I expected.
How can I debug if ALE is calling my powershell script? Does it even support it?
Beta Was this translation helpful? Give feedback.
All reactions