search

AtomLinter / linter-glsl

Atom package that lints GLSL shaders on the fly.
https://atom.io/packages/linter-glsl
MIT License
15 stars 6 forks source link

linter-glsl completely nonfunctional #106

Closed Vbbab closed 3 years ago

Vbbab commented 3 years ago

So I'm not sure if I'm missing something. I've followed the README instructions. I have copied a glslangValidator.exe into my working dir, and have configured linter-glsl to use it. However, upon loading up a .vsh file, typing some gibberish into it, and hitting save, no issues appear on the screen, as shown in this screenshot: image

From this image, you can see that I did, in fact install the linter-glsl package: image

Am I missing something here? Is there a key-combo to "begin" linting? Or is there an issue with something else (like plugin failed to initialize)?

Any help would be appreciated. If you would like me to attach logs of any kind, please tell me where they are and I will attach them if I can find them.

Thanks!

Vbbab commented 3 years ago

Also, it seems that glslangValidator says that the file passed as input can end in .<stage> for automatic file type detection. This .<stage> list does not contain fsh or vsh, so an option must be passed, i.e. -S frag for .fsh files and -S vert for .vsh files. Not sure if this is already accounted for in the package itself?

Vbbab commented 3 years ago

nvm, fixed it. Closing this issue. Turns out, linter-glsl doesn't look in the current working dir, it only looks on PATH.