Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation for Windows ClassPath for Managed service type #592

Open
pauby opened this issue May 30, 2023 · 0 comments
Open

Update documentation for Windows ClassPath for Managed service type #592

pauby opened this issue May 30, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@pauby
Copy link

pauby commented May 30, 2023

Describe the bug
I spent quite a bit of time troubleshooting this and discovered that the paths to be used on Windows are not the 'native filesystem separator' as specified in the Managed: Class Path help, but are Unix / Linux path separators.

The Chocolatey package that I maintain installs LanguageTool into c:\tools\languagetool.

This works:

image

This doesn't:

image

(Note the path separators)

To Reproduce
Hopefully the above gives enough information. If not, let me know.

Expected behavior
The help text for the Managed: Class Path entry in the Settings specifies that Unix / Linux style path separators are used.

Screenshots
Hopefully that's not needed.

Environment & Configuration (please complete the following information):

  • OS + Version: Windows 10
  • VS Code Version: 1.78.2 (2 weeks old).
  • LanguageTool Linter Version: 0.20.0
  • LanguageTool Version: 6.1
  • Service Configuration: managed
  • Service Classpath (if 'managed'): c:\tools\languagetool*.jar

Additional context
I appreciate that in the Wiki you don't provide any help for Windows. Hopefully this adds something.

@pauby pauby added the bug Something isn't working label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants