linting with atom.io on Windows10 w/ WLS?
dhartford opened this issue · comments
Hi,
First, extremely happy with any linter tooling integration into the atom.io IDE, that is such an important but often left to the side topic!
The RFE/bug item: on windows desktop...using ansible-lint with atom.io's plugins for the linters seems to be missing something. When using Windows 10 with ubuntu windows linux subsystem (WLS), I've added special proxy files (C:\wls\ansible-lint.bat that contain 'bash.exe -c "ansible-lint *%"') that when you use from regular windows commandline work as expected, however when I try to use this approach with the plugins it almost seems like nothing happens. Has anyone run into this or have tips of where to look?
Hi, sorry for taking so long to reply. I somehow forgot to. You may have luck on Stack Overflow with this question.
Hello.
I ran into the same issue. Looks to me, as if the ouput from ansible-lint is not interpreted correctly by the linter. Does not matter, if the path is in posix or windows notation.
Here is a sample output of my proxy scripts
C:\my_work\ansible\myfile.yml:8: [E201] Trailing whitespace
This should be shown as a linter issues, but is not!
Looks to me like a bug related to windows path handling.
Unfortunately, i do not know javascript and can not fix it myseld.
Could you please have a look?