Settings: Absolute paths with forward slashes '/' unsupported on Windows

[mfaux]

Possible bug with settings (vale.valeCLI.config). The README.md says that '/' is supported for Windows paths:

vale.valeCLI.config (default: null): Absolute path to a Vale configuration file. Use the predefined ${workspaceFolder} variable to reference configuration file from a custom location. (NOTE: On Windows you can use '/' ...

Forward slashes '/' work if my path is relative. However, for absolute paths, Vale cannot find my .vale.ini file.

For example, this works:

${workspaceFolder}/vale/.vale.ini

...but this fails:

/c/git/my-repo/vale/.vale.ini

As a work-around, \ is supported. The following works:

C:\git\my-repo\vale\.vale.ini

[jganser]

/c:/git/my-repo/vale/.vale.ini should work though :)

[ChrisChinchilla]

OK, I can take a look at this soon.

[michaeltlombardi]

@mfaux the reason for this is that on Windows, / maps to your home drive (usually C:)

I just tested locally and this worked for me (CLI installed via Chocolatey per the latest instructions in Vale's docs:

{
  // using / instead of C:\
  "vale.valeCLI.path": "/ProgramData/chocolatey/bin/vale.exe"
}

FWIW I didn't need this setting to work because Vale shows up in my normal executable PATH (you can confirm on windows with gcm vale | fl). Anecdotally though it does seem slightly faster.