Vale not linting on files opening from cmd line

[rohennes]

Hey,
(Using a linux machine)
When I open a folder in VS Code, then open a file in the file explorer view, Vale will lint the file as expected.

When I close VS Code, then open the same file from the cmd line, with no folder opened in VS Code, Vale doesn't lint at all.

I thought that previously (in the old version) I could open a file from the command line and Vale would lint the file?

I don't have an absolute path to a Vale config file set as there are different .vale.ini files in different folders.
Thanks!

[rohennes]

After further reading, it seems Vale runs in the context of a VS Code workspace. It would be nice if you opened a file from the cmd line and Vale linted it according to the relative .vale.ini config file. But that's a feature request. As a workaround I have added my home directory to a workspace. That seems to do the trick.

[ChrisChinchilla]

I have actually hit similar issues with VSCode before and I think it's a wider VSCode issue… For example I'll also see path and terminal environment issues in other plugins too. But I will take a look, however it could be something I can't fix.