-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add support for external LanguageTool servers #36
Comments
|
@Zplusless The newly implemented solution relies on the user starting the server, as mostly experts will use the server feature anyway. TeXstudio is a different story as it's written in C++ and thus needs to use LT as a server, in contrast to LTEX's Java core which can directly interact with LT. |
Fix released in 4.9.2. |
Reopening as the implementation depended on Java 11, which broke LTEX for some users (see #38). It's possible to implement this using a dependency, so this feature does not really on Java 11. Reverted this for now in 4.9.3. |
I'm currently running a server locally with docker for LanguageTools extension to not rely on external service. I'd like to not run the service multiple times 😄 |
I have reimplemented this using Java 8. Still needs to be tested though. It should make it to the 5.0 release. |
The new implementation is now in |
I will try it. Thanks. For information, here how I run a local LanguageTool server docker run --rm -p 9090:8010 --name languageTools erikvl87/languagetool Server address is http://127.0.0.1:9090 |
Fix released in 5.0.0. |
Is your feature request related to a problem? Please describe.
More advanced users might want to have their own instances of LanguageTool running on their local machines. For instance, in #34, there was a bug in LT that has been fixed in the development snapshot. Impatient users could run the LT server from the development snapshot for the fix, rather than having to wait for the next LT and LTEX release.
Describe the solution you'd like
Instead of using the built-in version of LT, connect to an LT server on localhost or wherever.
Describe alternatives you've considered
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: