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

Custom LanguageTool Server URL #221

Open
rpls opened this issue Jan 21, 2022 · 0 comments · May be fixed by #222
Open

Custom LanguageTool Server URL #221

rpls opened this issue Jan 21, 2022 · 0 comments · May be fixed by #222
Labels
enhancement New feature or request type: LanguageTool Issues related to LaguageTool

Comments

@rpls
Copy link

rpls commented Jan 21, 2022

I don't see any way of specifying a custom URL for an existing LanguageTool server, e.g., if you have the server running on your own (remote, not localhost) hardware. As far as I understand the shell code, it will use the public server if --server lt, and the localhost if it's --server my. Is it possible to specify a custom hostname? Custom port? For example, if --server is not in ["my", "lt", "stop"] to just use the argument as the server URL to specify --server https://mysuperserver/api/v2/check? Simplest patch would probably be: Check if cmdline.server is one of the keywords, if not, set the lt_server variable to the specified value (maybe with some pattern check if it's a valid URL) and set cmdline.server to "lt".

rpls added a commit to rpls/YaLafi that referenced this issue Jan 21, 2022
@rpls rpls linked a pull request Jan 21, 2022 that will close this issue
@torik42 torik42 added enhancement New feature or request type: LanguageTool Issues related to LaguageTool labels Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request type: LanguageTool Issues related to LaguageTool
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants